-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Erase type params when suggesting fully qualified path #96347
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
3 commits
Select commit
Hold shift + click to select a range
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
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
20 changes: 20 additions & 0 deletions
20
src/test/ui/traits/do-not-mention-type-params-by-name-in-suggestion-issue-96292.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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
struct Thing<X>(X); | ||
|
||
trait Method<T> { | ||
fn method(self, _: i32) -> T; | ||
} | ||
|
||
impl<X> Method<i32> for Thing<X> { | ||
fn method(self, _: i32) -> i32 { 0 } | ||
} | ||
|
||
impl<X> Method<u32> for Thing<X> { | ||
fn method(self, _: i32) -> u32 { 0 } | ||
} | ||
|
||
fn main() { | ||
let thing = Thing(true); | ||
thing.method(42); | ||
//~^ ERROR type annotations needed | ||
//~| ERROR type annotations needed | ||
} |
37 changes: 37 additions & 0 deletions
37
src/test/ui/traits/do-not-mention-type-params-by-name-in-suggestion-issue-96292.stderr
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
error[E0282]: type annotations needed | ||
--> $DIR/do-not-mention-type-params-by-name-in-suggestion-issue-96292.rs:17:11 | ||
| | ||
LL | thing.method(42); | ||
| ------^^^^^^---- | ||
| | | | ||
| | cannot infer type for type parameter `T` declared on the trait `Method` | ||
| this method call resolves to `T` | ||
|
||
error[E0283]: type annotations needed | ||
--> $DIR/do-not-mention-type-params-by-name-in-suggestion-issue-96292.rs:17:11 | ||
| | ||
LL | thing.method(42); | ||
| ------^^^^^^---- | ||
| | | | ||
| | cannot infer type for type parameter `T` declared on the trait `Method` | ||
| this method call resolves to `T` | ||
| | ||
note: multiple `impl`s satisfying `Thing<bool>: Method<_>` found | ||
--> $DIR/do-not-mention-type-params-by-name-in-suggestion-issue-96292.rs:7:1 | ||
| | ||
LL | impl<X> Method<i32> for Thing<X> { | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
... | ||
LL | impl<X> Method<u32> for Thing<X> { | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
help: use the fully qualified path for the potential candidates | ||
| | ||
LL | <Thing<_> as Method<i32>>::method(thing, 42); | ||
| ++++++++++++++++++++++++++++++++++ ~ | ||
LL | <Thing<_> as Method<u32>>::method(thing, 42); | ||
| ++++++++++++++++++++++++++++++++++ ~ | ||
|
||
error: aborting due to 2 previous errors | ||
|
||
Some errors have detailed explanations: E0282, E0283. | ||
For more information about an error, try `rustc --explain E0282`. |
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.
Not sure if this is overkill, but we could know exactly what generic types need to be erased if we returned the impl's
DefId
fromfind_similar_impl_candidates
instead of just theTraitRef
, then we might just be able to use subst instead of erasing all type paramsThere 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.
🤔 maybe, but that'd end up being a relatively larger change, right?
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.
yeah, but it might allow us to erase fewer type variables when we're calling one generic method from another generic method with type variables.
but probably not worth the effort...