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 cc34883
Browse filesBrowse the repository at this point in the historyBrowse files
Shrink the compiled and hand-written floors: the dependent walks, dependency clearing, status writes, effect-run queueing, flatten's thunk walk and the delegated-event parent hop share their code (no behavior change).
A memo on the observation lifecycle (unowned, or `lazy: true`) that blocked on an async source is no longer released before the retry its source's landing queued (#4474). The settle walk re-enqueues the blocked reader and, finding it unobserved, released it on the spot: the release pulled the retry back out of the heap, so the memo never computed the landing and woke later with no value — `latest()` of it returned `undefined` beside `isPending() === true`. The release now waits for that pass (`REACTIVE_RELEASE_AFTER`): the retry runs once, as the owned twin's does, and the node is released at the pass's tail if it is still unobserved and settled. #2934's contract is kept (no perpetual recompute — one pass, then the release), #3078's untouched (reads revive; a dormant memo dirtied in the same tick is still reclaimed before the heap). Laziness is never observable (D-22).
fix(signals): a re-parked node drops pending sources its pass no longer reaches, so a `<Loading>` whose first answer was superseded while a sibling refetched reveals once both settle (#4541)
Copy file name to clipboardExpand all lines: packages/signals/docs/RULES-FUNDAMENTALS.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,7 @@ These are the only words the fundamentals use. Internal names (transaction, stag
98
98
99
99
**Immutable.** `isPending(x)` is `true` iff `x`'s value is not the final answer to a _new question_: an input changed and the new answer has not been committed, a landed answer waits in a hold, or in-flight work declared it will change the data (`affects()`). It is `false` the moment the value is final. Re-asking the same question — `refresh()`, polling, an action's confirming refetch — is quiet: the shown value still answers, `isPending` stays `false`, and the fresh value reveals silently; to make a reload read as pending, declare it (`affects(x); refresh(x)`). A node with no committed value has nothing to judge, so it has no verdict: a first load, or a memo born held over a held value (D-2). It is _loading_ — inside an owner `isPending` of it does what the read itself does: a first load's `NotReadyError` goes to a boundary or holds, and a reader of a memo born held is held with it (caught by a boundary that has not shown content, F-4, or held with the change, F-2) and runs at the commit, where the answer is final. No answer is shown before then. Unowned, `isPending` of it is `false` (D-24). `latest` of it is its pending value if it has one (a memo born held) and throws if it has none (a first load) (D-22). A declared first paint (`loadingValue`) is loading too. Optimistic values are verdict-inert: an optimistic write never makes its own slot pending and never silences anything. Pending is per node — per store key — never store-wide. For a node with a committed value, painting does not decide it: where `x`'s readers are — on screen, behind a fallback, in a branch not yet attached — does not change `isPending(x)`, and `latest(x)` is the newest value it has produced (D-22). A verdict on content that may have no committed value belongs inside the boundary that owns that content (D-23).
100
100
101
-
**What it does not say.** It does not say `isPending` can be `true` on creation (it cannot — hydration parity; a memo born held has no verdict until its commit). It does not say an action in progress is pending data (process affordances are co-written state, not verdicts).
101
+
**What it does not say.** It does not say `isPending` can be `true` on creation (it cannot — hydration parity; a memo born held has no verdict until its commit). It does not say an action in progress is pending data (process affordances are co-written state, not verdicts). It does not say a boundary's first frame cannot show `true`: "on creation" is the node's, not the screen's — a node whose first answer lands beside the write that re-asks it (#4459), or while an upstream re-ask has it pending by propagation (#4569), is committed and pending, and content that reads only its verdict reveals with it (D-23, S-40).
Copy file name to clipboardExpand all lines: packages/signals/docs/SCENARIOS.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -698,6 +698,23 @@ _Ruled 2026-10-09, from the read-order brief's sibling case (416). Not D-28: thi
698
698
| ✗ || sibling `0`, slot `(empty)`| neither the fallback nor `1` — the boundary waited on `n0`, which it did not read |
699
699
| ✗ || sibling `0 \| loading`| the same wait, shown as a fallback |
700
700
701
+
**The verdict form (ruled 2026-10-31, #4569; D-23, #3373):** a fresh `<Loading>` whose content reads only `isPending` of a first load reveals when the verdict exists. `a0 = async(s)`, `a2 = async(await a0())`; `a0:0` lands, `a2` asks `a2:11`; `setS(1)` re-asks `a0` and marks `a2` pending by propagation while `a2:11` is up and `a2` has no value; `a2:11` lands. `a2`'s question changes only when `a2` re-runs, so the answer is current: `a2` is committed and pending on `a0`. Content that reads `a2` holds (F-2: no screen to keep) — the asymmetry is the rule.
| ✗ || after 3: `loading`|| rejected: a first load kept loading by a supersession no rule has |
715
+
716
+
Pinned: `tests/first-load-superseded-answer-4569.test.ts` (also a 3-deep chain and the no-boundary root, which attaches at 3 with `pending`), `packages/web/test/first-load-superseded-answer-4569.spec.tsx`.
717
+
701
718
### S-45. A first answer landing in the same tick as an action that writes its input: `latest` shows it, the plain read waits — D-22, F-9 (async generator E9)
702
719
703
720
_Ruled 2026-10-28. The leaf form and the through-a-memo form show the same screen; today the leaf keeps the fallback up until the action ends — that is the ✗ row._
0 commit comments