Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Add an expected-guided simplification step to state error derivations

未关闭
#297 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
java
领域
compilers

调研方向

Start in liquidjava-verifier/src/main/java/liquidjava/processor/refinement_checker/VCChecker.java at VCChecker.throwStateRefinementError, where Expected and the simplified Found expression are available. Trace the expression and state-set information used for the derivation history, then verify that the new “Relevant to this requirement” step preserves necessary facts, supports backward navigation, and leaves verification results unchanged.

由索引模型根据 Issue 内容生成。

描述

Problem

The final Found step in a state error can contain facts from state sets unrelated to Expected. The user must identify the relevant fact and trace version equalities manually.

Current example

The last simplification step for preview.setTiling(...) is:
Image

Expected concerns the tiling state of preview³⁰⁴. The relevant startTiling(preview²⁹⁹) fact and the version link are present, but compression facts remain in the final explanation.

Desired behavior

Append a step labeled “Relevant to this requirement” after the existing simplification steps when the verifier can safely produce one. In this example, it should retain startTiling(preview²⁹⁹) and the equality needed to relate its tiling state to preview³⁰⁴. It should omit compression facts only if their independence from this requirement has been established. The back arrow should return to the full step shown above.

This is a simplification step in the error display. It must not change the verification condition checked by the solver or the verification result.

Implementation direction
  1. Give the new pass both Expected and the simplified Found expression. VCChecker.throwStateRefinementError has both when it constructs the error.
  2. Use expression and state set information to identify the receiver, relevant state set, and necessary version equalities.
  3. Remove a clause only when its independence has been established. Keep clauses whose role is uncertain.
  4. Append the result to the derivation history with the metadata needed for source links and backward navigation. Do not infer dependencies from rendered names.
Acceptance criteria
  • The scanner error gains a final “Relevant to this requirement” step showing the startTiling fact and every necessary version link.
  • Proven independent compression facts are omitted; uncertain facts remain.
  • The existing full step remains available through the back arrow.
  • No step is added when safe cleanup cannot be established.
  • Verification results do not change.
主要语言
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 摘要。