-
Notifications
You must be signed in to change notification settings - Fork 13.8k
Add a diagnostic for similarly named traits #144674
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
Open
rperier
wants to merge
1
commit into
rust-lang:master
Choose a base branch
from
rperier:add_note_if_a_type_impl_a_trait_with_the_same_name
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
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
Some comments aren't visible on the classic Files Changed page.
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
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
2 changes: 1 addition & 1 deletion
2
compiler/rustc_trait_selection/src/error_reporting/traits/mod.rs
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
Oops, something went wrong.
Oops, something went wrong.
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.
when is
self.tcx.crate_name(trait_def_id.krate) == krate && self.tcx.item_name(trait_def_id) == name
false butself.tcx.def_path_str(trait_def_id) == required_trait_path
holds?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.
It used by
tests/ui/traits/bound/same-crate-name.rs
, disabling this case makes the test fail.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.
so that's
crate::mod::Trait
andcrate::Trait
?Wait, disabling which case? Each of the two cases should handle some distinct cases I would expect, what are the test covering eacvh of them and could we generalize the condition even further. It feels weird to have 2 different conditions if the rest of the diagnostic is exactly the same
Uh oh!
There was an error while loading. Please reload this page.
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.
No, I am not talking about my test "tests/ui/traits/similarly_named_trait.rs" , but about https://github.com/rust-lang/rust/blob/master/tests/ui/traits/bound/same-crate-name.rs#L10 instead. Removing the line "self.tcx.def_path_str(trait_def_id) == required_trait_path" makes this test fail. I think the use case covered by this test is real, isn't it ?
Uh oh!
There was an error while loading. Please reload this page.
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 have investigated. This test checks for ambiguities regarding the full import path, the import path is the same for both crates here, while the crates name are differents. The first crate name is
crate_a1
, the second crate name iscrate_a2
the item name isBar
. So we havecrate_a1::Bar
,crate_a2::Bar
, in both cases the import name ismain::a::Bar
. I could of course, update the test, but I think that what the test is checking for might be a real use case.