OpenE2K/rust
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

diagnostics for E0432: imports are relative to crate root

Browse Source 
This is curiously missing from both the short message and this
long diagnostic.

Refs #31573 (not sure if it should be considered "fixed" as the
short message still only refers to extern crates).
This commit is contained in:
Georg Brandl 2016-05-01 20:40:16 +02:00
parent 2a815a26c8
commit d20b4067fd
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
src/librustc_resolve/diagnostics.rs
View File

@ -916,11 +916,14 @@ An import was unresolved. Erroneous code example:
use something::Foo; // error: unresolved import `something::Foo`.
```
Please verify you didn't misspell the import name or the import does exist
in the module from where you tried to import it. Example:
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:
```ignore
use something::Foo; // ok!
use self::something::Foo; // ok!
mod something {
pub struct Foo;
@ -928,7 +931,7 @@ mod something {
```
Or, if you tried to use a module from an external crate, you may have missed
the `extern crate` declaration:
the `extern crate` declaration (which is usually placed in the crate root):
```ignore
extern crate homura; // Required to use the `homura` crate