-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Only emit one error for use foo::self;
#42580
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
Conversation
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
@@ -11,4 +11,7 @@ | |||
use foo::self; //~ ERROR unresolved import `foo::self` |
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 guess if foo
is invalid we should still have both errors?
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 don't think it makes sense to improve errors in this area, all examples from #42559 should be legal anyway, I'll try to submit a PR somewhere after June 17.
r? @jseyfried or @petrochenkov |
@bors r+ |
📌 Commit 4640f4d has been approved by |
⌛ Testing commit 4640f4d with merge 5b5fcca... |
Currently `use foo::self;` would emit both E0429 and E0432. This commit silence the latter one (assuming `foo` is a valid module). Fixes rust-lang#42559
Fixed the tests |
@bors r+ |
📌 Commit b89db83 has been approved by |
Only emit one error for `use foo::self;` Currently `use foo::self;` would emit both E0429 and E0432. This commit silence the latter one (assuming `foo` is a valid module). Fixes #42559
☀️ Test successful - status-appveyor, status-travis |
Currently
use foo::self;
would emit both E0429 and E0432. This commit silence the latter one (assumingfoo
is a valid module).Fixes #42559