architecture

The parser uses a templated ParserInline that devirtualizes SAX callbacks, tiered double conversion (Clinger, Eisel-Lemire, from_chars), SIMD whitespace and escape scanning, and zero-copy string_views for escape-free strings. Speculative key matching lets handlers consume raw key bytes before escape scanning.

Nesting is capped at 1024 open containers via strata::kMaxNestingDepth, enforced in ParserInline before the handler sees the container. Exceeding it raises ValueError with a distinct message, sized for a 6.4x safety margin on Windows' 1 MB stack.

No. The C++ DOM stores numbers as double only, so integers above 2^53 lose precision in DOM-based paths like CompiledPath.execute. The Python SAX path via PythonObjectBuilder preserves exact integers at any size.

The dead-code map lists count_object_keys, fast_dtoa, arena_allocator, parse_int_fast, collect_newlines_simd, on_uint, and others. These have no callers and must not be built upon; the map is maintained in the architecture documentation.

FlatMap is an insertion-ordered vector of pairs with linear-scan lookup, chosen for cache locality on typical small objects. Its emplace appends without duplicate checks because the parser's duplicate-key policy depends on find returning the first match.