Skip to content

items.use.restrictions.extern-prelude: be more clear example succeed only in 2015 edition #2327

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.

Sign up for GitHub

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

Open
tshepang wants to merge 1 commit into
base: master
Choose a base branch
from
+4 −2
Open

items.use.restrictions.extern-prelude: be more clear example succeed only in 2015 edition #2327

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions src/items/use-declarations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -443,11 +443,13 @@ r[items.use.restrictions.extern-prelude]
> ```

> [!EDITION-2018]
> In the 2015 edition, the prefix `::` refers to the crate root, so `use ::{self as root};` is allowed because it is same as `use crate::{self as root};`. Starting with the 2018 edition the `::` prefix refers to the extern prelude, which cannot be directly imported.
> In the 2015 edition, the prefix `::` refers to the crate root, so `use ::{self as root};` is allowed because it is same as `use crate::{self as root};`.
>
> ```rust,edition2015
> use ::{self as root}; //~ Ok
> use ::{self as root}; //~ Ok in 2015 edition
> ```
>
> Starting with the 2018 edition, the `::` prefix refers to the extern prelude, which cannot be directly imported.

r[items.use.restrictions.duplicate-name]
As with any item definition, `use` imports cannot create duplicate bindings of the same name in the same namespace in a module or block.
Expand Down
Loading