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 e8dcf6c
Browse filesBrowse the repository at this point in the historyBrowse files
The comment above the pass's previous value in `recompute` now says a lane node's lane value is used only when the slot holds one, matching the guarded expression beneath it. The #3955 test now covers `createMemo(fn)` beside `createSignal(fn)`, asserts that the landing after the equal lane passes flushes without throwing and records only arrays, and resets a halted system after each case so each case fails on its own pre-fix. The changeset describes the thrown `prev is not iterable` instead of the internal marker.
Copy file name to clipboardExpand all lines: .changeset/fix-lane-derivation-prev-3955.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 derivation re-running under a lane whose first pass was equal receives its committed value as `prev`instead of the empty `NOT_PENDING` marker.
5
+
A `createSignal(fn)` or `createMemo(fn)`derivation that reads `latest()` or `isPending()` of a signal an in-flight async memo is holding receives its previous value as `prev`on every re-run under the hold. When its first pass under the hold was equal to the previous value, the next pass received an empty internal marker instead, so `(prev = []) => [...prev]` threw `prev is not iterable` and halted the reactive system.
0 commit comments