-
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
path suggestions in Rust 2018 should point out the change in semantics #55185
Conversation
This comment has been minimized.
This comment has been minimized.
2a5dc5e
to
d2baf92
Compare
@bors r+ |
📌 Commit d2baf92 has been approved by |
path suggestions in Rust 2018 should point out the change in semantics Fixes rust-lang#55130. This commit extends existing path suggestions to link to documentation on the changed semantics of `use` in Rust 2018. r? @nikomatsakis
This comment has been minimized.
This comment has been minimized.
d2baf92
to
ad0ac6a
Compare
@bors r=nikomatsakis |
📌 Commit ad0ac6aa1a290c59e4a189a5a0b002ed0d5d3c07 has been approved by |
This comment has been minimized.
This comment has been minimized.
ad0ac6a
to
8d5fb4c
Compare
@bors r=nikomatsakis |
beta-nominating for RC2 inclusion; I think this would be nice to have though not critical |
path suggestions in Rust 2018 should point out the change in semantics Fixes rust-lang#55130. This commit extends existing path suggestions to link to documentation on the changed semantics of `use` in Rust 2018. r? @nikomatsakis
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This commit extends existing path suggestions to link to documentation on the changed semantics of `use` in Rust 2018.
8d5fb4c
to
0d06b8c
Compare
@bors r=nikomatsakis |
📌 Commit 0d06b8c has been approved by |
path suggestions in Rust 2018 should point out the change in semantics Fixes rust-lang#55130. This commit extends existing path suggestions to link to documentation on the changed semantics of `use` in Rust 2018.
Rollup of 11 pull requests Successful merges: - #55148 (Implement FromStr for PathBuf) - #55185 (path suggestions in Rust 2018 should point out the change in semantics) - #55191 (Fix sub-variant doc display) - #55199 (Impl items have generics) - #55244 (Don't rerun MIR passes when inlining) - #55252 (Add MaybeUninit::new) - #55257 (Allow extern statics with an extern type) - #55389 (Remove unnecessary mut in iterator.find_map documentation example, R…) - #55406 (Update string.rs) - #55412 (Fix an ICE in the min_const_fn analysis) - #55421 (Add ManuallyDrop::take)
[beta]: Prepare the 1.31.0 beta release * Update to Cargo's branched 1.31.0 branch * Update the channel to `beta` Rolled up beta-accepted PRs: * #55362: Remove `cargo new --edition` from release notes. * #55325: Fix link to macros chapter * #55358: Remove redundant clone (2) * #55346: Shrink `Statement`. * #55274: Handle bindings in substructure of patterns with type ascriptions * #55297: Partial implementation of uniform paths 2.0 to land before beta * #55192: Fix ordering of nested modules in non-mod.rs mods * #55185: path suggestions in Rust 2018 should point out the change in semantics * #55423: back out bogus `Ok`-wrapping suggestion on `?` arm type mismatch Note that **this does not update the bootstrap compiler** due to #55404
Some( | ||
"`use` statements changed in Rust 2018; read more at \ | ||
<https://doc.rust-lang.org/edition-guide/rust-2018/module-system/path-\ | ||
clarity.html>".to_string() |
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 am getting a 404 not found when visiting https://doc.rust-lang.org/edition-guide/rust-2018/module-system/path-clarity.html
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.
yes, that URL isn't live yet, but will be as of the next release
Fixes #55130.
This commit extends existing path suggestions to link to documentation
on the changed semantics of
use
in Rust 2018.r? @nikomatsakis