solidjs / solid / 43187075785

79%

main: 90%

push

github

fix(signals): a landing's re-derived memo re-runs the held runs that read it stale (#4794)

At a hold's landing, a sync memo that read the screen while the hold was
up (a verdict reader: `[latest(x), x()]` or `isPending` beside a held
write) re-derives as a stale reader. The held runs of its readers were
computed on its stale pass, and were released first, so the landing frame
showed the old `x` beside the landed value for one frame (F-1, A15). The
memo form tore where the inline form did not.

The lane engine's landing hook (`adoptParked`) now voids those runs and
re-queues the readers, so they re-run on the memo's re-derived value. An
async memo's re-ask keeps the runs it reveals with. Core floor 0 B.


Claude-Session: https://claude.ai/code/session_0117BoWNSSgtemsSYsaX2hXE

Co-authored-by: Claude <noreply@anthropic.com>

818 of 1112 branches covered (73.56%)

Branch coverage included in aggregate %.

1143 of 1372 relevant lines covered (83.31%)

30.35 hits per line