Add an expected-guided simplification step to state error derivations
まだ誰も着手していません。
評価
調査の方向性
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分
- マージ済み PR（30日）
- 2
環境構築
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
liquid-java/liquidjava のほかの issue
-
enhancement error messages future ide
難易度 5/5 1週間以上 初心者へのやさしさ 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 が 118 日前に担当しましたが、オープン中のプルリクエストはありません。 オープン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
-
feature triaged
難易度 1/5 1時間未満 初心者へのやさしさ 75/100
Graylog2/graylog2-server#27549 ·
メンテナーはふだん 1 日以内に返信
-
component/zeebe kind/bug
難易度 1/5 1時間未満 初心者へのやさしさ 90/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
UniversalMediaServer/UniversalMediaServer#6356 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
googleapis/google-cloud-java#14533 ·
メンテナーはふだん 1 日以内に返信