rust/tests/ui/imports/import3.stderr

error[E0432]: unresolved import `main`
  --> $DIR/import3.rs:1:5
   |
LL | use main::bar;
   |     ^^^^ use of unresolved module or unlinked crate `main`
   |
help: you might be missing a crate named `main`, add it to your project and import it in your code
   |
LL + extern crate main;
   |

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0432`.
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			error[E0432]: unresolved import `main`
compiletest: Require `//~` annotations even if `error-pattern` is specified 2025-03-29 02:41:32 +03:00			`--> $DIR/import3.rs:1:5`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			`\|`
			`LL \| use main::bar;`
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` ``` 2024-11-18 03:42:16 +00:00			\| ^^^^ use of unresolved module or unlinked crate `main`
suggest `extern crate foo` when failing to resolve `use foo` fix ci error 2022-05-22 11:48:35 +09:00			`\|`
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` ``` 2024-11-18 03:42:16 +00:00			help: you might be missing a crate named `main`, add it to your project and import it in your code
Structured suggestion for `extern crate foo` when `foo` isn't resolved in import When encountering a name in an import that could have come from a crate that wasn't imported, use a structured suggestion to suggest `extern crate foo;` pointing at the right place in the crate. When encountering `_` in an import, do not suggest `extern crate _;`. ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 \| LL \| use spam::*; \| ^^^^ maybe a missing crate `spam`? \| help: consider importing the `spam` crate \| LL + extern crate spam; \| ``` 2024-07-24 19:31:02 +00:00			`\|`
			`LL + extern crate main;`
			`\|`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00
			For more information about this error, try `rustc --explain E0432`.