rust/tests/ui/unresolved/unresolved-asterisk-imports...

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

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0432`.
fix invalid `unresolved imports` errors the asterisk wildcard syntax causes use a path variabale 2022-03-04 12:07:39 +08:00			error[E0432]: unresolved import `not_existing_crate`
			`--> $DIR/unresolved-asterisk-imports.rs:1:5`
			`\|`
			`LL \| use not_existing_crate::*;`
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-24 03:43:46 +08:00			\| ^^^^^^^^^^^^^^^^^^ you might be missing crate `not_existing_crate`
suggest `extern crate foo` when failing to resolve `use foo` fix ci error 2022-05-22 10:48:35 +08: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-25 03:31:02 +08:00			help: consider importing the `not_existing_crate` crate
			`\|`
			`LL + extern crate not_existing_crate;`
			`\|`
fix invalid `unresolved imports` errors the asterisk wildcard syntax causes use a path variabale 2022-03-04 12:07:39 +08:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 23:44:16 +08:00			`error: aborting due to 1 previous error`
fix invalid `unresolved imports` errors the asterisk wildcard syntax causes use a path variabale 2022-03-04 12:07:39 +08:00
			For more information about this error, try `rustc --explain E0432`.