Repository navigation
docs(WO17): parity harness audit — 408/433, one semantic catch (fixed), three normalizer notes - #432
Merged
Merged
Conversation
…ment fix (#842); hardening finding recorded
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Step 4a landed: the cross-grammar parity harness (maps #270, single new file) audits all 434 corpus files through both the ts and py parsers — 408/433 structurally identical, 6 divergence kinds in four stories. The one SEMANTIC story (py's use-with-override placement splitting the pass) is already fixed in interscript-ruby #842 with failing-first specs; the other three are normalizer-level notes that the generated-parser switch (step 4b) resolves at the root. Also recorded: the EOF-spin hardening finding for both hand parsers (synthetic repro hangs at 100% CPU; corpus safe today).