solidjs / solid / 34249390117

72%

main: 89%

push

github

docs(signals): createDeferred proposal — verify seams, resolve open questions

Verification pass against lanes.ts / optimistic.ts / verdict.ts / async.ts:

- Landing path is asyncWrite's existing lane branch; the only addition is
  ensuring a lane at landing time. Lanes never merge into transitions and a
  deferred node is never a reporter, so its lane is never held.
- refresh(deferred) would resolve stale (waiter relies on the read parking);
  fixed by D9: authoritative readers bypass the clamp, per the A17 precedent.
- isPending rides the affects() mark channel (markWalk reachability +
  _repollVerdicts), verdict-only — pending does not propagate through
  derivations of a deferred node since they never re-run. Mark is a
  flight-lifecycle flag, not _inFlight (never nulled at landing) and not a
  transaction refcount.
- Lane merge with an in-flight optimistic action is the correct semantics
  (one convergence rule, one paint at settle), not an accepted coupling.
- Adds §2.2 (what the user sees), §2.3 (how to teach it: consistency by
  default, staleness by declaration; latest is input-side, deferred is
  data-side), §9 (migration role with loadingValue).
- Rejects the <Deferred> boundary and the createMemo option outright.
- D3 sharpened; D9, D10 added; CONFIG_DEFERRED = 1 << 19.

Co-authored-by: Cursor <cursoragent@cursor.com>

516 of 784 branches covered (65.82%)

Branch coverage included in aggregate %.

768 of 1002 relevant lines covered (76.65%)

14.99 hits per line