-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Update Error 0432 long description for Rust 2018 #71413
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
The examples and reasoning in the long description were for Rust 2015 and are unnecessary or wrong in Rust 2018.
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ecstatic-morse (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
|
||
``` | ||
use core::any; // No extern crate required in Rust 2018! | ||
# fn main() {} |
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 need for this one.
|
||
In Rust 2018, the `extern crate` declaration is not required and you can instead just `use` it: | ||
|
||
``` |
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.
You'll need to add edition2018
to make it work I think.
|
||
In Rust 2018, paths in `use` statements are relative to the current module unless they begin with the name of a crate or a literal `crate::`, in which case they start from the crate root. As in Rust 2015 code, the `self::` and `super::` prefixes refer to the current and parent modules. | ||
|
||
Also verify that you didn't misspell the import |
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.
You can fill the line more you know. :)
@BookOwl any updates? |
Closing due to inactivity. Feel free to reopen or open another PR if you want to restart working on this, thanks! |
…GuillaumeGomez Update E0432 long description with the separate behaviors of editions 2015 and 2018 Fixes rust-lang#64668. I restarted from the work done in rust-lang#71413.
The examples and reasoning in the long description for Error code 0432 (unresolved import) were for Rust 2015 and are unnecessary or wrong in Rust 2018.
This PR resolves issue #64668.