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.
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
Tweak E0277 highlighting and "long type" path printing #132086
Tweak E0277 highlighting and "long type" path printing #132086
Changes from all commits
24ac777
aa82fd6
5980a32
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Question [PATH-PREFIX 1/2]: does it make sense to pull
long_ty_file
toTypeErrCtxt
?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.
@jieyouxu it would. We need to pull
long_ty_file
all the way up as much as possible. This was the minimal patch that would address the issue we noticed.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.
Ah, I see I've ran into this exact problem before in #121739 (comment)
EDIT: posted this on the wrong review comment chain.
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.
Discussion [PATH-PREFIX 2/2]: I believe this is one of the places where we will leak the path prefix even with
-Z remap-path-prefix
or-Z remap-cwd-prefix
or-Z remap-path-scope=diagnostics/all
. Should the file path here also go through those? If it's possible to pull thelong_ty_file
toTypeErrCtxt
, would it be better if handling path prefix remapping happens there too?To be clear, I'm not saying this should be done in this PR, just as a remark that this can be a potential issue.
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.
That's a good point. We should have a single method for printing the long type paths
note
, properly handling that case.