bjoernager/rust
bjoernager/rust
1
Fork 0
Code Activity

E0432: rust 2018 -> rust 2018 or later in --explain message

Browse source
This commit is contained in:
Matthias Krüger 2022-06-06 11:39:54 +02:00
parent 6609c6734d
commit 343c135e0c
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
compiler/rustc_error_codes/src/error_codes/E0432.md
View file

@ -10,10 +10,10 @@ In Rust 2015, paths in `use` statements are relative to the crate root. To
import items relative to the current and parent modules, use the `self::` and import items relative to the current and parent modules, use the `self::` and
`super::` prefixes, respectively. `super::` prefixes, respectively.
In Rust 2018, paths in `use` statements are relative to the current module In Rust 2018 or later, paths in `use` statements are relative to the current
unless they begin with the name of a crate or a literal `crate::`, in which module unless they begin with the name of a crate or a literal `crate::`, in
case they start from the crate root. As in Rust 2015 code, the `self::` and which case they start from the crate root. As in Rust 2015 code, the `self::`
`super::` prefixes refer to the current and parent modules respectively. and `super::` prefixes refer to the current and parent modules respectively.
Also verify that you didn't misspell the import name and that the import exists Also verify that you didn't misspell the import name and that the import exists
in the module from where you tried to import it. Example: in the module from where you tried to import it. Example:
@ -38,8 +38,8 @@ use core::any;
# fn main() {} # fn main() {}
``` ```
In Rust 2018 the `extern crate` declaration is not required and you can instead Since Rust 2018 the `extern crate` declaration is not required and
just `use` it: you can instead just `use` it:
```edition2018 ```edition2018
use core::any; // No extern crate required in Rust 2018. use core::any; // No extern crate required in Rust 2018.