solidjs / solid / 41503451738

78%

main: 89%

push

github

fix(signals): an inherited verdict posture reads the hold's own write (#4544) (#4625)

A pass whose verdict posture is only inherited (it read a memo that calls
isPending/latest, and neither it nor its node's last pass opened a window of
its own) is the hold's work where it reads the hold's own sync write: it is
served that staging and joins the hold. The branch a hold opens then reads
the hold's world and the hold lands, in one flush() or several (F-10).
Before the flush parks, such a read leaves the verdict lane an earlier read
of the verdict memo seated the pass in.

A staging a window asked of under the hold that holds it (or in this flush)
still reads as the screen, so `[latest(x), x()]` through a memo stays atomic
(A10, D-26). The mark (`_askedIn`) names that hold and expires with it:
nothing sticky. CONFIG_OWN_PROBE is renewed by every pass from
REACTIVE_WINDOW.

A pass that probes in its own body stays the hold's verdict reader (F-6).
When a render effect born into the hold reads such a reader's settled value
and goes pending on what that display-ahead value asks for, the pending no
longer holds the hold (CONFIG_AHEAD, F-6): the hold lands and the reader
re-derives at the landing (A15). A lane's reveal still waits (S-29).

Everything is gated on the verdict engine's hooks.


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

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

803 of 1104 branches covered (72.74%)

Branch coverage included in aggregate %.

1131 of 1369 relevant lines covered (82.62%)

29.91 hits per line