First-class obstruction strands for Supported Outcome Settlement

Aperta
  • Qualcosa non va?
#116 2 commenti 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
28/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
rust
Ambito
compilers, documentation

Direzione di ricerca

Start with the topic shelf at docs/topics/obstruction-strands/README.md and issue #113 for Echo/target-IR context. The work is language design: keep current require ... else terminal, then specify a distinct AST/Core/Target IR disposition (e.g. continue_obstructed_strand) so obstruction is not hidden control flow and records no success-path write. Done means the syntax topic and IR notes match the acceptance criteria; there is no Edict milestone yet.

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

Descrizione

documentation enhancement release:continuum-stack release:target-ir release:target-profiles

Goal

Design first-class Edict syntax/lowering for preserved repairable obstruction attempts.

Topic shelf: docs/topics/obstruction-strands/README.md.

Thesis

Current Edict require ... else <obstruction> is terminal. It means the success path cannot proceed, no success-path write occurs, and a typed obstruction returns.

Future resumable obstruction must be first-class syntax, not an ordinary function call hidden inside else.

Potential future shape:

require jim.basisFresh(input.basis)
  else continue obstructed jim.EditObstruction.StaleBase {
    providedBasis: input.basis,
    draftDigest: hash("Draft", input.content),
    repair: jim.RepairHint.RebaseRequired,
  };

Supersedes / refines

  • Refines #113 by ensuring Echo execution bridge work can later report terminal obstruction vs preserved repairable obstruction distinctly.
  • Refines target-IR planning with a future continue_obstructed_strand disposition.
  • Keeps support tier policy outside Edict: Edict defines/lower artifacts; consuming authorities decide settlement support obligations.

Acceptance criteria

  • The syntax topic clearly states terminal obstruction remains the current contract.
  • Future syntax has a distinct AST/Core/Target IR disposition.
  • else continueInObstructedStrand(...) is not treated as hidden control flow.
  • Target IR planning records no success-path write on obstruction.
  • Echo/Jim can later witness preserved obstruction attempts as causal material.

Milestone

No Edict milestone exists yet; attach to the next target-IR/Continuum-stack milestone when one is created.

Lingua principale
Rust
Stelle
0
Fork
0
Nessuna PR unita negli ultimi 30g

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 flyingrobots/edict

Tutte le issue di flyingrobots/edict

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.