-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Unify "input" and "no input" paths in run_compiler
#118002
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
706eb16
Rename `early_error_handler` as `default_handler`.
nnethercote 8aee35e
Merge `interface::run_compiler` calls.
nnethercote 446c8e0
Move `describe_lints` calls.
nnethercote 5659cc5
Factor out two `print_crate_info` calls.
nnethercote 472f7c9
Simplify `run_compiler` control flow.
nnethercote File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think the new name is any better. It is only supposed to be used for error handling very early on. After the Session is created it should't be used anymore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, there is
EarlyErrorHandler used after the session is created. Within the
interface::run_compiler` call there is this:The idea is that
default_handler
as a name contrasts more clearly withhandler
thanearly_error_handler
does. Because they both have typeEarlyErrorHandler
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All uses of
let handler = EarlyErrorHandler::new(sess.opts.error_format);
haveSession
passed in as argument and thus should work withsess.fatal("...");
just fine. I think it would make sense to remove allEarlyErrorHandler
usage whensess
is in scope and remove theerror_format
argument fromEarlyErrorHandler
.