Skip to content

Commit 6060f26

Browse files
test(async-gen): S-60 — the #4544 arm as a ruling row (#4743)
Co-authored-by: tembo[bot] <208362400+tembo-io[bot]@users.noreply.github.com> Co-authored-by: tembo[bot] <208362400+tembo[bot]@users.noreply.github.com>
1 parent 366c0eb commit 6060f26

6 files changed

Lines changed: 406 additions & 360 deletions

File tree

‎packages/signals/docs/RULES-DERIVED.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,7 @@ True while an input change is held, while `x`'s own flight for a new question is
160160

161161
### D-25. A display-ahead read never holds the change it reads ahead of; its reader's own async holds the reader
162162

163-
**From:** F-6, F-1, F-3. **Rows:** S-27, S-29, S-30, S-31, S-39, S-40, S-46, S-49, S-50, S-51, S-52, S-58. **Pins also:** `tests/ispending-combined-atomic-3442.test.ts`, `tests/verdict-memo-held-branch-4544.test.ts`, `tests/latest-memo-inline-parity.test.ts`, `tests/lane-render-effect-grouping-4284.test.ts`, `tests/display-ahead-plain-write-content.test.ts`.
163+
**From:** F-6, F-1, F-3. **Rows:** S-27, S-29, S-30, S-31, S-39, S-40, S-46, S-49, S-50, S-51, S-52, S-58, S-60. **Pins also:** `tests/ispending-combined-atomic-3442.test.ts`, `tests/verdict-memo-held-branch-4544.test.ts`, `tests/latest-memo-inline-parity.test.ts`, `tests/lane-render-effect-grouping-4284.test.ts`, `tests/display-ahead-plain-write-content.test.ts`.
164164

165165
A pass's posture is decided by its own reads in that pass, never inherited from a creator or a memo it reads (#4544) and never carried into its next run. Each `latest` or `isPending` read sees the hold's world and joins nothing. A plain read of a node this pass also read ahead is the screen's: the two channels of one node agree within a scope, so `[x(), isPending(x)]` shows `[committed, true]` now in either order (A10, S-27). A memo that hoists that pair keeps the screen it had inline (S-52, 2026-11-07): the display, not the probe, is what makes the pair showable. A plain read of any other held value makes the pass the hold's work (D-1): a mixed `on` waits (S-49), and a memo that probed on its last run and probes nothing on this one holds the tick (S-50, both ruled 2026-11-05). Whether a read throws is that read's own: an earlier display-ahead read does not disarm a later plain read's throw (S-39). A branch a display-ahead read gates is not derived from it: a mount under `<Show when={latest(x) > 0}>` is a mainline mount whose plain reads are the screen's — `latest(x)` inside shows ahead at its own site — and a first pass under it that reads the hold's staging is born held (D-1), attaching at the landing, on its fallback inside a `<Loading>` (S-31, S-46). A render effect off a lane that reads what the lane is revealing — mounted mid-hold, or re-run by an unrelated write — shows the committed value and re-derives at the reveal (S-30). What is rendered from a display-ahead read waits for that read's own async, as one reveal (S-29). A display-ahead pass shows; it never asks (F-6's limit, 2026-11-07): the display — a render effect, a compiled binding, a user effect, and the sync derivations feeding them — holds the value it showed beside the verdict, in a render effect or a memo alike (S-52; hoisting the pair into a memo changes no screen), and an async derivation that reads a held value plainly, or `isPending` of one, is the hold's, asking once, of the truth (S-51, #4677; ruled and built 2026-11-07) — a pass that asks is a verdict reader only by a window of its own, never by reading a verdict memo (#4504). A user effect's callback runs at the frame it belongs to, lane or mainline; async in an effect is the author's.
166166

0 commit comments

Comments
 (0)