Repository navigation
docs(signals): clarify untrack with async reads - #4169
Conversation
|
Merging this PR will degrade performance by 10.7%
|
| Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|
| ❌ |
build + consume |
694.3 µs | 777.5 µs | -10.7% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing Neekoras:docs-1635-untrack-async (ad4d7e4) with next (71153bf)
Footnotes
-
5 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩
Refs solidjs/solid-docs#1635.
The Solid 2
untrackreference is generated from this JSDoc. Explain thatuntrackprevents dependency tracking but does not suppress an unresolved async read: the owning computation still suspends and retries when the source first settles. The text also distinguishesisPendingandlatestfrom an initial fallback, and showsloadingValuefor a read that must return immediately.This changes documentation only. The existing
autodispose-contract,strict-read-pending-store, andloading-valuetests cover the behavior described. Prettier andgit diff --checkpass locally.Prepared with Codex AI assistance and checked against the current source and tests.