mirror of
https://github.com/larvit/adf-codec.git
synced 2026-11-19 06:35:44 +01:00
Answer architecture round 1: 2 🔴, 5 🟡; readableBlock alone fills and reads the spelling memo, the escaper's steps hand on what they claim rather than write a shared buffer, engine-limit names only the throws an engine returns, and the docs agree on it
This commit is contained in:
+5
-5
@@ -467,11 +467,11 @@ handles one cause alike whichever node, attribute or direction raised it.
|
||||
causes the bound (§The code list). A carried node passes it on about 1 MB of deeply nested JSON,
|
||||
since the block carry indents two spaces a level; `todo.md` item 107 respells the carry in a
|
||||
length linear in its JSON (2026-10-11).
|
||||
- A conversion the engine stops, by running short of memory or passing its longest array, is
|
||||
`engine-limit`, at the empty path. A retry may pass it, so `unsupported-node-shape`, which never
|
||||
does, cannot hold it. JavaScriptCore throws the same `Out of memory` past its longest string,
|
||||
which takes `engine-limit` too: telling the two apart would mean reading the engine's message
|
||||
(2026-10-13, the maintainer).
|
||||
- A conversion the engine stops with a throw of its own, past its longest array, `Map` or `Set`
|
||||
or short of memory, is `engine-limit`, at the empty path. A retry may pass the memory case, so
|
||||
`unsupported-node-shape`, which no retry passes, cannot hold the class. JavaScriptCore throws the
|
||||
same `Out of memory` past its longest string, which takes `engine-limit` too, since only the
|
||||
message would tell the two apart (2026-10-13, the maintainer).
|
||||
- The markdown readers and `htmlToAdf` refuse a value that is not a string as `not-a-string`, at
|
||||
position `{ line: 1, offset: 0 }` with an empty path: no existing code reads true of it, and
|
||||
`not-an-adf-document` names the emitters' input (2026-10-05).
|
||||
|
||||
Reference in New Issue
Block a user