Repository navigation
Commit dc33de6
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 <[email protected]>1 parent 9c917ea commit dc33de6
4 files changed
Lines changed: 81 additions & 3 deletions
File tree
- .changeset
- packages/signals
- docs
- src/core
- tests
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
0 commit comments