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 摘要。