-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
error: unresolved name a::b::c
[E0425] doesn't indicate which component doesn't exist
#30926
Comments
Hum, indeed. it's even more obvious with code like this: mod a {}
fn main() {
a::b::x;
} However, it also precises that |
Interesting that we have ended up with two distinct error codes (E0425 and E0433) that seem to indicate the same thing, as far as I can tell. This probably arose because the I'd like to see if we could combine the two variants, and in the process, improve the error for E0425 in this case. (Combining the two variants would just be an internal improvement; it is probably not strictly necessary for resolving this issue.) Note that both variants carry along a |
I'm gonna take a look (if you don't do it before me). |
I believe this has been fixed (cc #32789). Edit: at least the example provided by GuillaumeGomez. |
Great! I close it then. |
The unresolved name error message should indicate which path component it can't resolve.
For example:
Here we are unable to tell if
imp
orpayload
doesn't resolve.The text was updated successfully, but these errors were encountered: