nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-22 06:44:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

Rollup merge of #97787 - matthiaskrgr:e0432_explain, r=Dylan-DPC

Browse Source 
E0432: rust 2018 -> rust 2018 or later    in --explain message
This commit is contained in:
Dylan DPC 2022-06-06 14:34:59 +02:00 committed by GitHub
commit 99afe26032
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show Stats 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
`super::` prefixes, respectively.
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 respectively.
In Rust 2018 or later, 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 respectively.
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:
@ -38,8 +38,8 @@ use core::any;
# fn main() {}
```
In Rust 2018 the `extern crate` declaration is not required and you can instead
just `use` it:
Since Rust 2018 the `extern crate` declaration is not required and
you can instead just `use` it:
```edition2018
use core::any; // No extern crate required in Rust 2018.