Parent: #496 Related: #493, #480, #544
Problem
After an oversized decimal BigInt literal fails the i128 fast path, canonicalDecimalDigits duplicates the complete digit span into the parser arena. Decimal literal validation has already rejected leading-zero forms, so an unseparated literal's source slice is canonical and immutable. A separated literal is likewise canonical after stripSeparators, which already owns its exact normalized bytes. The final duplicate therefore adds one full-width allocation and copy without changing the value.
Scope
- Commit parser-only 1K/2K/4K unseparated decimal BigInt rows plus a separated 4K same-value control before changing the lexer.
- Validate every canonical output byte and retain exact checksums, source construction, warmup, and timed-boundary metadata.
- Borrow the validated source slice for unseparated oversized decimal BigInts.
- Reuse the exact normalized buffer for separated oversized decimal BigInts.
- Preserve small/large BigInt values, raw token text, source offsets, invalid leading-zero/separator behavior, OOM propagation, and arena lifetimes.
No-workaround rules
- No pre-normalized scored source, source construction in the timed boundary, skipped full-value validation, reduced widths, hash/cache recognition, lazy conversion that moves work outside the boundary, or different values in the separated control.
- No arbitrary literal-length limit and no relaxation of adversarial-complexity or memory bounds.
- Do not modify stacks, queues, jobs, Promise/microtask behavior, or Thread/Worker lifecycle.
Acceptance
- Benchmark-first rows freeze exact 1K/2K/4K values, same-value separated control, checksums, warmup, and parser-only timed boundaries.
- Exact-parent evidence reports wall, retired instructions, logical allocation requests/bytes, RSS, dispersion, and identical checksums.
- Unseparated oversized decimal BigInts allocate no canonicalization storage; separated forms retain exactly one normalization allocation.
- Small/large values, invalid leading zeros/separators, raw text, offsets, lifetime, and OOM witnesses pass.
- Focused lexer/frontend, full units, decimal/BigInt test262 coverage, and TSan pass with no regressions.
- Raw evidence and report are checked in before any public performance claim.