-
Notifications
You must be signed in to change notification settings - Fork 1.7k
associated type is unresolved when trait path is qualified. #11973
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
Labels
A-nameres
name, path and module resolution
C-bug
Category: bug
S-actionable
Someone could pick this issue up and work on it right now
Comments
Probably dupe of #8282. |
I swear I searched 🤣 |
I don't think this is the same issue though, because 8282 has the trait in scope, where as this issue refers to it having a qualified path for the trait. I'll reopen but feel free to close if it is indeed dupe. |
I think the two is same. the both try to resolve a path fully. and the last segment is a assoc of trait. |
the diff is need to fix different method |
lnicola
added a commit
to lnicola/rust-analyzer
that referenced
this issue
Apr 27, 2022
This reverts commit 5d1aff3.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-nameres
name, path and module resolution
C-bug
Category: bug
S-actionable
Someone could pick this issue up and work on it right now
When
T2
is used ast2::T2
,Bar
is unresolved, but when usingT2
directly by getting it in scope w/use t2::T2;
, it is resolved properly.rust-analyzer version: 14c86d5 2022-04-13 dev
rustc 1.60.0 (7737e0b5c 2022-04-04)
The text was updated successfully, but these errors were encountered: