generalise warning suppression #1020
Merged
Conversation
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
Member
lsf37
commented
Jan 5, 2023
•
lsf37
commented
- use a set of suppressed warnings
- add API for warning suppression
- add CLI for warning suppression
- add lex spec directives for warning suppression
- add to docs
This should make all remaining uses of plain string warnings obsolete. Depcrecates `void warning(String message)`.
The only remaining uses are now in test cases.
- keep a set of configurable warnings in ErrorMessages - CLI: add --warn-all/--no-warn-all to switch on/off all warnings - CLI: --warn-<warning> enables a warning - CLI: --no-warn-<warning> suppresses a warning
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.