refactor: Use Config::emit_diagnostic to emit warnings#12531
Closed
Muscraft wants to merge 1 commit intorust-lang:masterfrom
Closed
refactor: Use Config::emit_diagnostic to emit warnings#12531Muscraft wants to merge 1 commit intorust-lang:masterfrom
Config::emit_diagnostic to emit warnings#12531Muscraft wants to merge 1 commit intorust-lang:masterfrom
Conversation
Collaborator
|
r? @weihanglo (rustbot has picked a reviewer for you, use r? to override) |
Contributor
|
☔ The latest upstream changes (presumably #12573) made this pull request unmergeable. Please resolve the merge conflicts. |
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.
#12235 is tracking user control over warnings. Part of the effort means moving warnings from being emitted by
ShelltoConfig. This is for a few reasons:Shellshould not know what a user wants to do with a given warning other than emit anything that is passed to itConfigshould (eventually) know what a user wants to do for each warningcargois attempting to display, be thatforbid,deny,warn, orallow.In both scenarios, it makes sense to move things to
Config, which is what this PR does. It adds a new functionConfig::emit_diagnostic, which is a copy ofShell::warn, and moves all calls fromShell::warnto this new function.