You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 10f3cc8
Browse filesBrowse the repository at this point in the historyBrowse files
♻️ Hand a REPL entry's computed root data back on its own result (#939)
The per-binding publication protocol #939 shipped is removed whole: no
producer, mode, admission field, parser, counter, outcome marker or
expansion plumbing, and nothing renamed in its place. `expand.ts`,
`generated-xmd.ts`, `host.ts` and the CLI's `entries.ts` return to the
pre-#939 base byte for byte.
In its place, an execution computes the root data it hands back. A binding
is a byproduct of running the document, so one private owner per canonical
invocation is given the actual root environment by identity, and at the
result boundary it reads that root's current eligible data onto the
ordinary `DocumentResult` — on an authored failure as well as on success,
because a failure is an outcome. The journal gains no operation, and
`parseDocumentResult` stays the single interpretation point, so a cold
reader answers from the record it already parses.
Reading is owned the same way. `useSecretDetection` now returns the
disclosure policy beside the journal gate, so the owned read closes over
the exact scanner the gate closes over and a later same-name Context
cannot weaken it. `HostExecution.bindings()` exposes that read, and
`ReplSession.bindings()` layers it over the retained head, rechecking the
running entry's identity after the read suspends.
Ordinary authored failures now normalize inside the canonical result
boundary. Before this, a plain `<Fail>` left no `DocumentResult` at all —
the root Close held the durable protocol's serialized error — so its
rendered text was lost to every later reader. Durability and fatal Files
failures still escape ahead of it.
0 commit comments