Skip to content

Commit ec5965a

Browse files
ryansolidclaude
andauthored
docs(signals): F-12 — try/catch in a memo does not catch an upstream memo's error (#4410) (#4422)
Errors are status: a reader of an errored memo is errored with it, and recovery goes through <Errored>. A promise the reader awaits itself is its own throw and try/catch catches it. Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2 Co-authored-by: Claude <[email protected]>
1 parent e82efb0 commit ec5965a

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎packages/signals/docs/RULES-FUNDAMENTALS.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,7 @@ These are the only words the fundamentals use. Internal names (transaction, stag
122122

123123
**Immutable.** An error thrown by content under an `<Errored>` sends that boundary to its error fallback, which is then the display (F-3): readers behind it hold nothing. A pending read is never an error: `<Errored>` does not catch it and never shows its fallback for a wait, and `ASYNC_OUTSIDE_LOADING_BOUNDARY` is a warning, not a failure. An error that escapes every boundary halts the reactive system (`REACTIVITY_HALTED`); later writes are ignored. In effects, compute-phase errors can be intercepted (`createEffect`'s error arm) and are logged and skipped when they are not; effect-phase errors escalate to the nearest boundary.
124124

125-
**What it does not say.** It does not say an error clears on the next write — the error fallback stays until a new answer replaces the errored one (D-39). It does not say an error shows before the frame it belongs to: an error is an answer — it ends the wait like a value, and it shows when a value would (D-41).
125+
**What it does not say.** It does not say an error clears on the next write — the error fallback stays until a new answer replaces the errored one (D-39). It does not say an error shows before the frame it belongs to: an error is an answer — it ends the wait like a value, and it shows when a value would (D-41). It does not say a `try`/`catch` in a memo or effect catches an upstream memo's error: an error is the upstream memo's status, not a throw the reader owns, so a reader that reads an errored memo is errored with it whether or not it catches the read, and recovery goes through `<Errored>` (ruled 2026-10-29, #4410). A rejected promise the reader awaits itself is the reader's own throw: `try`/`catch` around the `await` catches it like any exception.
126126

127127
**Collapses:** A1–A6, §23.1 items 2–3 (2026-10-01), the 7b re-pin (2026-10-02), recovery 9.1/9.2. **Derived:** D-38, D-39, D-41. **Scenarios:** S-38, S-42, S-43.
128128

0 commit comments

Comments
 (0)