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 4a89b84
Browse filesBrowse the repository at this point in the historyBrowse files
perf(signals): shrink the fresh-Loading hold wait (#4593, #4591)
One inline loop at the boundary seam instead of `waitHeld` and its two
closures: no `.some`/`forEach`, no CONFIG_OVERRIDE mask or lane check, no
held-output guard (a swap held in the same hold folds back as before),
every held input recorded rather than the first. The #2937 exemption is
now `!txOf(h)._open`: a first load re-asked under an open action reveals at
its landing; under a plain write's hold (parked only while a flight the
screen waits on is out) it waits for the commit.
Hydrating (Show/For/Loading/Errored/lazy), local rolldown: +257 -> +145 B
minified over next; floors unchanged.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_0117BoWNSSgtemsSYsaX2hXE
Copy file name to clipboardExpand all lines: .changeset/loading-reveal-waits-held-write-4593.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,4 +2,4 @@
2
2
"@solidjs/signals": patch
3
3
---
4
4
5
-
A `<Loading>` that has not shown content no longer reveals content derived from a write still held outside it (F-7, F-1). Two reveals did not consult the hold: a first load the held write re-asked (kept out of every hold, #2937) landed mainline and revealed its answer beside a screen still showing the frame before the write (#4593); and a reader settled by an answer staged in the hold — a rejection, which marks no frame reader (D-41) — revealed the content's stale committed value under a re-armed `on` boundary and let the held write commit early (#4591). The boundary now waits on the held node and reveals with that hold's commit; the rejection shows when a value for the same question would. A first load whose held write the screen shows nowhere still reveals at its landing (#2937).
5
+
A `<Loading>` that has not shown content no longer reveals content derived from a write still held outside it (F-7, F-1). Two reveals did not consult the hold: a first load the held write re-asked (kept out of every hold, #2937) landed mainline and revealed its answer beside a screen still showing the frame before the write (#4593); and a reader settled by an answer staged in the hold — a rejection, which marks no frame reader (D-41) — revealed the content's stale committed value under a re-armed `on` boundary and let the held write commit early (#4591). The boundary now waits on the held node and reveals with that hold's commit; the rejection shows when a value for the same question would. A first load re-asked under an open action still reveals at its landing (#2937).
0 commit comments