solidjs / solid / 38681392232

78%

main: 89%

push

github

feat: createDeferred, an async memo that may lag but never leads (D-40) (#4067)

* feat: createDeferred, an async memo that may lag but never leads (D-40)

Amends F-1/F-2 with a declared-lag exception: once a createDeferred node
has answered, its refetches hold nothing. Readers keep the committed value,
isPending reports the flight (on the node, its derivations and derived
store leaves), refresh() is a quiet re-ask, and until/await refresh wait
for the landing. A refetch that read a held input lands with that hold.

Built on the loading window, CONFIG_REDERIVE and a mark per flight; the
mark core moves out of affects into affects-marks.ts so createDeferred can
reuse it. Server createDeferred is createMemo; hydration goes through the
signal-like adapter.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S2HrYgWeGJX6hKw7bD5LQN

* feat(createDeferred): carry #3710's pins; a held re-ask joins nothing (D11)

Ports #3710's signals tests (D1-D11, mizulu's graph), its web and
hydration specs and the deferred-settled-element harness scenario, and
makes them pass:

- D11: an answered deferred node carries CONFIG_LAGS; recompute's T4 arm
  does not join its held re-pass to the hold, and the wrapper serves the
  staged landing as the pass's value, so the write commits mainline and
  the hold keeps the landing it took.
- until over a derivation is released by an equal-value landing: the
  mark's repoll re-runs truth readers too (not through a derived store,
  whose leaves re-run them at the derive's write).
- The lag walk hops a store slot to its family's derive.

The disposal pin is rewritten to this PR's behaviour (the mark drops at
disposal). Treeshake pins cover the deferred module and the mark core.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S2HrYgWeGJX6hKw7bD5LQN

* perf(createDeferred): the derive carries its famil... (continued)

755 of 1046 branches covered (72.18%)

Branch coverage included in aggregate %.

2 of 2 new or added lines in 1 file covered. (100.0%)

1086 of 1328 relevant lines covered (81.78%)

27.73 hits per line