Restore fast typed decoding for ordinary transcripts
This commit is contained in:
@@ -146,6 +146,12 @@ and processes case variants in the baseline key order. The decoder keeps
|
||||
numeric tokens intact. Schema tests cover superseded and effective type
|
||||
mismatches, both case-variant orders, and exact IDs in both envelopes.
|
||||
|
||||
The follow-up restores direct typed decoding for ordinary segment arrays.
|
||||
Arrays with conflicting or escaped keys use compatibility decoding where
|
||||
needed. Both envelopes were verified with mixed segments. On the same
|
||||
100,000-segment fixture, median parse time fell from about 0.83 to 0.30
|
||||
seconds and allocation fell from 162 to 78 MB per parse.
|
||||
|
||||
**Affected plan:** Stage 5, item 1.
|
||||
|
||||
**Evidence:** The baseline selected the final value of an exact duplicate JSON
|
||||
|
||||
Reference in New Issue
Block a user