rust/tests/ui/macros/builtin-prelude-no-accidents.rs
Esteban Küber dd52bfc76e Reword "crate not found" resolve message
```
error[E0432]: unresolved import `some_novel_crate`
 --> file.rs:1:5
  |
1 | use some_novel_crate::Type;
  |     ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `some_novel_crate`
```

On resolve errors where there might be a missing crate, mention `cargo add foo`:

```
error[E0433]: failed to resolve: use of unresolved module or unlinked crate `nope`
  --> $DIR/conflicting-impl-with-err.rs:4:11
   |
LL | impl From<nope::Thing> for Error {
   |           ^^^^ use of unresolved module or unlinked crate `nope`
   |
   = help: if you wanted to use a crate named `nope`, use `cargo add nope` to add it to your `Cargo.toml`
```
2025-01-24 01:19:50 +00:00

9 lines
413 B
Rust

// Names of public modules in libstd and libcore don't accidentally get into prelude
// because macros with the same names are in prelude.
fn main() {
env::current_dir; //~ ERROR use of unresolved module or unlinked crate `env`
type A = panic::PanicInfo; //~ ERROR use of unresolved module or unlinked crate `panic`
type B = vec::Vec<u8>; //~ ERROR use of unresolved module or unlinked crate `vec`
}