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 5600428
Browse filesBrowse the repository at this point in the historyBrowse files
fix(signals): a memo of latest() computes once on a plain write; a Loading fallback behind an error keeps the error up
- A transaction only a `latest()` read opened holds nothing: a verdict
reader's plain read of a staging in it, from the frame's seat, is the
frame's read, watched by the seam, which re-derives it once only if the
flush parks (D-22, F-10). So `[s(), L()]` with `L = createMemo(() =>
latest(s))` computes once per write, as the inline form does (F-6), and
the inline form beside such a memo does too. Lane work still sees the
screen (D-37).
- A Loading boundary catching under an error boundary that shows its
fallback records the reader on the error boundary too: the inner
fallback is hidden behind the error, which stays until the re-ask
answers (D-39) — a body read now shows `[E]` like an effect read.
- Pins: runs-once over inline, memo, inline beside a memo, latest(memo) ×
memo, render effect, user effect (two writes); JSX inline/memo ×
attributes/template; the D-39 body read.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2
0 commit comments