solidjs / solid / 37687846246

76%

main: 89%

push

github

fix(signals): a new async memo created over a hold lands its first answer into it (#3800) (#3881)

* fix(signals): a new async memo created over a hold lands its first answer into it (#3800)

A memo created while a transaction holds a value, whose first pass reads
that value and returns a promise, was a loading source the seam does not
hold (plan sec. 15.2), so its answer landed as mainline commit #0 and its
readers showed the held future beside the committed page. The same memo
with a synchronous first answer is born held (A29). The first pass now
records the transaction it was born into under the born-held arm's
conditions (a joined read, or a verdict lane's mount reading a staging),
and its first landing is staged into that transaction while it is live.
The hold never waits for the first load (the direction rule, #3820).

Maintainer clarification (2026-10-07): the #3869 ruling covers new memos
that don't read async; a new memo that reads the held world is held,
async first answer included.

Co-authored-by: Claude via Cursor <noreply@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

* chore(size): size exception for a new async memo's first landing into its hold (#3800)

Raises seventeen caps to CI brotli + 10 B with their recorded minified,
from Size run 37684843282 against next @ dafad1db3 — the frozen core,
simple-app, hydrating and live-page floors among them. Accepted by the
maintainer 2026-10-07 on the condition hello world stays under 10 KB
(CI: 9,914 B).

Co-authored-by: Claude via Cursor <noreply@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

---------

Co-authored-by: Claude via Cursor <noreply@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

674 of 958 branches covered (70.35%)

Branch coverage included in aggregate %.

996 of 1227 relevant lines covered (81.17%)

28.57 hits per line