Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add an expected-guided simplification step to state error derivations

Aperta
  • Qualcosa non va?
#297 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java
Ambito
compilers

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
Java
Stelle
67
Fork
36
Merge medio
7g 48m
PR unite (30g)
2

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di liquid-java/liquidjava

Tutte le issue di liquid-java/liquidjava

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.