You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test: pin the primary reject message, not the farthest-exploration hint (#45)
Wiring emit-reject-messages to the full TS corpus (the new emit-parity CI job)
exposed a pre-existing divergence on bigintPropertyName.ts: emit and the
interpreter report the SAME primary error ("unexpected 'const' after successful
parse" at the same offset) but a different `[farthest: …]` hint (offset 318 vs
316). It is not a regression — master diverges identically — and it is on master,
not introduced here.
The hint is the parser's exploration high-water mark, and the two engines run
deliberately-independent control loops (the interpreter prunes an inline alt the
emitter still tries — issue #45 D1 / #54), so they can reach it differently in
rare error cases. emit-parser-verify proves the CST is byte-identical across all
18,805 files, so a farthest-only difference never affects correctness. Pin the
primary error (the consumer contract); report farthest-only differences but don't
fail. Confirmed against the full corpus: 0 primary mismatches, 1 farthest-only.
0 commit comments