rust/tests/ui/imports/issue-1697.stderr

error[E0432]: unresolved import `unresolved`
  --> $DIR/issue-1697.rs:3:5
   |
LL | use unresolved::*;
   |     ^^^^^^^^^^ you might be missing crate `unresolved`
   |
help: consider importing the `unresolved` crate
   |
LL + extern crate unresolved;
   |

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0432`.
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			error[E0432]: unresolved import `unresolved`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-1697.rs:3:5`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| use unresolved::*;`
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 \| LL \| use spam::*; \| ^^^^ you might be missing crate `spam` \| = help: consider adding `extern crate spam` to use the `spam` crate ``` 2024-07-23 19:43:46 +00:00			\| ^^^^^^^^^^ you might be missing crate `unresolved`
suggest `extern crate foo` when failing to resolve `use foo` fix ci error 2022-05-22 11:48:35 +09:00			`\|`
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			help: consider importing the `unresolved` crate
			`\|`
			`LL + extern crate unresolved;`
			`\|`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07: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`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
			For more information about this error, try `rustc --explain E0432`.