Repository navigation
Conversation
Adds a "Let a panel lag" section to the async reactivity concept page, a row for it in the update decision table, and caveats on the reference page contrasting it with reading every consumer through latest (solidjs/solid#4773). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117BoWNSSgtemsSYsaX2hXE
|
|
✅ Deploy Preview for solid-docs-v2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description(required)
solidjs/solid#4773 asks when to reach for
createDeferred, and suggests it is the same as reading every consumer throughlatest. It is not:latestchanges what one reader shows while the update stays held for every other reader, whereas a deferred memo is not part of the update at all, so nothing waits for it.createDeferred" section after thelatestone, using the page's own dashboard (the ten-second audit panel). It contrasts reader-sidelatestwith source-sidecreateDeferred, says when to use each, and notes that a deferred memo lags but never leads (its first load still suspends; a refetch that reads a held value lands with that hold). The update decision table gains a fourth row pointing to it.createDeferredreference: a Caveats section with the same distinction. It is added toENTRY_CAVEATSinscripts/extract-solid-ref.mjsand written into the generated page by hand. A fullsync:refrun against currentnextstops on an unrelated new export (verdict) that has no disposition yet.The semantics follow Solid's ruling for deferred sources (D-40: a deferred source lags its readers and never leads them).
Related issues & labels
createDeferredv2 documentation: when should it be used overcreateMemo? solid#4773Generated by Claude Code