Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Add an expected-guided simplification step to state error derivations

Offen
  • Stimmt etwas nicht?
#297 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
java
Bereich
compilers

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
Java
Sterne
67
Forks
36
Ø Merge
7 T. 48 Min.
Gemergte PRs (30 T.)
2

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus liquid-java/liquidjava

Alle Issues in liquid-java/liquidjava

Ähnliche Issues

Weitere Issues zu Java

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.