Skip to content

Commit

Permalink
Auto merge of #73562 - poliorcetics:e0432-to-edition2018, r=Guillaume…
Browse files Browse the repository at this point in the history
…Gomez

Update E0432 long description with the separate behaviors of editions 2015 and 2018

Fixes #64668.

I restarted from the work done in #71413.
  • Loading branch information
bors committed Jul 7, 2020
2 parents 70f9d23 + 5970136 commit 51eeabf
Showing 1 changed file with 25 additions and 10 deletions.
35 changes: 25 additions & 10 deletions src/librustc_error_codes/error_codes/E0432.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,27 +6,42 @@ Erroneous code example:
use something::Foo; // error: unresolved import `something::Foo`.
```

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. 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 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.

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:

```
use self::something::Foo; // ok!
use self::something::Foo; // Ok.
mod something {
pub struct Foo;
}
# fn main() {}
```

Or, if you tried to use a module from an external crate, you may have missed
the `extern crate` declaration (which is usually placed in the crate root):
If you tried to use a module from an external crate and are using Rust 2015,
you may have missed the `extern crate` declaration (which is usually placed in
the crate root):

```
extern crate core; // Required to use the `core` crate
```edition2015
extern crate core; // Required to use the `core` crate in Rust 2015.
use core::any;
# fn main() {}
```

In 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.
# fn main() {}
```

0 comments on commit 51eeabf

Please sign in to comment.