Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Restore alias expansion in refinement diagnostic history

未關閉
#295 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
48/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
java
領域
compilers

研究方向

Start by tracing the VC simplification history that replaced the earlier alias derivation work in issues #160, #184, and #261. Add a regression test for the E_A2_04_CsvChunker mismatch or an equivalent found-versus-expected refinement failure. Done means failed checks retain structured alias expansions for both refinements, including substituted definitions and navigation back to alias names.

由索引模型根據 Issue 內容生成。

描述

Alias expansion is used when checking a refinement, but the current VC simplification history does not record it. The earlier alias derivation feature from #160 and #184 was removed during the migration to VC simplification in #261.

For example, E_A2_04_CsvChunker reports Expected: Positive(buffered), Found: Nat(buffered), and counterexample buffered == 0. Here Nat(x) means x >= 0 and Positive(x) means x > 0, but the diagnostic contains no step that reveals those definitions.

Preserve the alias expansions used in a failed check as structured diagnostic data for both the found and expected refinements. A client should be able to show the substituted definitions and navigate back to the alias names. Add a regression test for this example or an equivalent mismatch.

主要語言
Java
星號
67
分支
36
平均合併
7 天 48 分鐘
30 天內合併 PR
2

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

liquid-java/liquidjava 的其他 Issue

查看 liquid-java/liquidjava 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。