Repository navigation
Add back +legacy-comparison to the validate project - #12394
Open
philderbeast wants to merge 43 commits into
Open
philderbeast wants to merge 43 commits into
philderbeast wants to merge 43 commits into
Conversation
+legacy-comparison to the validate project+legacy-comparison to the validate project
5 of 6 tasks
- Add haddocks for flagToDebugInfoLevel
- Legacy parser gave Flag "" - Parsec parser gives NoFlag
- Add readConfigDiverging
philderbeast
force-pushed
the
test/validate-comparing-parsers
branch
from
October 8, 2026 13:25
1f6f086 to
36190b2
Compare
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.
A follow on from #12139 (depends-on: 12139), adding back
+legacy-comparisonto the validate project, something that was removed in #11773.significance: significantin the changelog file.