Add an expected-guided simplification step to state error derivations
還沒有人認領這個 Issue。
評估
研究方向
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:
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
- Give the new pass both Expected and the simplified Found expression.
VCChecker.throwStateRefinementErrorhas both when it constructs the error. - Use expression and state set information to identify the receiver, relevant state set, and necessary version equalities.
- Remove a clause only when its independence has been established. Keep clauses whose role is uncertain.
- 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
startTilingfact 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
環境準備
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
liquid-java/liquidjava 的其他 Issue
-
enhancement error messages future ide
難度 5/5 一週以上 新手友好度 35/100
liquid-java/liquidjava#298 ·
-
難度 4/5 3-5 天 新手友好度 55/100
liquid-java/liquidjava#296 ·
-
難度 4/5 3-5 天 新手友好度 48/100
liquid-java/liquidjava#295 ·
-
Add a flag -a to show all verification conditions sent to the smt solver可能重新可做 @CatarinaGamboa 於 116 天前認領，目前沒有進行中的 PR。 未關閉enhancement
liquid-java/liquidjava#240 · 已指派 1 人 ·
-
enhancement ide
難度 3/5 1-2 天 新手友好度 45/100
liquid-java/liquidjava#206 ·
查看 liquid-java/liquidjava 的全部 Issue
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 78/100
openhab/openhab-core#5847 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 75/100
-
bug
難度 2/5 1-3 小時 新手友好度 76/100
-
難度 2/5 1-3 小時 新手友好度 88/100
apache/parquet-java#3820 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
beehive-lab/jllm#187 ·