-
Notifications
You must be signed in to change notification settings - Fork 152
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This PR removes the `strict` field in `ParseInModule`. The field is safe to remove because, after eliminating some dead code, - The only use of `strict` in `ParseInModule` is in `parseStringTerm` - `strict` is (almost) always set to `true` - The only place where `strict` is set to `false` is through a few calls to `RuleGrammarGenerator.getCombinedGrammar` in `KPrint`. However, these usages only ever call `getParsingModule` and `getExtensionModule` on the constructed `ParseInModule` object, neither of which invokes `parseStringTerm`, so the value of `strict` here is actually irrelevant. Note that no actual functionality is lost either - the only live usage of `strict` in `parseStringTerm` is now fully controlled by the `inferSortChecks` argument rather than `strict && inferSortChecks`. Co-authored-by: rv-jenkins <[email protected]>
- Loading branch information
1 parent
ce5b128
commit 9a8e0a7
Showing
16 changed files
with
72 additions
and
119 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.