-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Added the documentation for the 'use' keyword #72761
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
Fix suggestions from review. Co-authored-by: Bastian Kauschke <[email protected]>
@lcnr Since |
I think an example would be helpful here, but as this feature is very rarely used, a link to |
There is a link to this page already (though not the exact section), the one named as [Reference], should repeat it once more (with the exact section) or is okay with what's already here ? |
Seems good to me 👍 |
r? @Dylan-DPC @bors r+ rollup |
📌 Commit 4bae9e5 has been approved by |
Rollup of 10 pull requests Successful merges: - rust-lang#72026 (Update annotate-snippets-rs to 0.8.0) - rust-lang#72583 (impl AsRef<[T]> for vec::IntoIter<T>) - rust-lang#72615 (Fix documentation example for gcov profiling) - rust-lang#72761 (Added the documentation for the 'use' keyword) - rust-lang#72799 (Add `-Z span-debug` to allow for easier debugging of proc macros) - rust-lang#72811 (Liballoc impl) - rust-lang#72963 (Cstring `from_raw` and `into_raw` safety precisions) - rust-lang#73001 (Free `default()` forwarding to `Default::default()`) - rust-lang#73075 (Add comments to `Resolve::get_module`) - rust-lang#73092 (Clean up E0646) Failed merges: r? @ghost
This is a partial fix of #34601.
I heavily inspired myself from the Reference on the
use
keyword.I checked the links when compiling the documentation, they should be ok.
I also added an example for the wildcard
*
in the case of types, because it's behaviour is not import everything like one might think at first.