os-rust/tests/ui/imports/issue-55457.stderr

error[E0432]: unresolved import `NonExistent`
  --> $DIR/issue-55457.rs:1:5
   |
LL | use NonExistent;
   |     ^^^^^^^^^^^
   |     |
   |     no `NonExistent` in the root
   |     help: a similar name exists in the module: `non_existent`

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

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0432`.
resolve: Fix ICE in macro import error recovery 2018-10-30 00:21:39 +03:00			error[E0432]: unresolved import `NonExistent`
			`--> $DIR/issue-55457.rs:1:5`
			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| use NonExistent;`
use structured suggestions for E0432 2019-01-16 15:30:41 -05:00			`\| ^^^^^^^^^^^`
			`\| \|`
			\| no `NonExistent` in the root
			\| help: a similar name exists in the module: `non_existent`
resolve: Fix ICE in macro import error recovery 2018-10-30 00:21:39 +03:00
			error[E0432]: unresolved import `non_existent`
			`--> $DIR/issue-55457.rs:2:5`
			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| use non_existent::non_existent;`
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 `non_existent`
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 `non_existent` crate
			`\|`
			`LL + extern crate non_existent;`
			`\|`
resolve: Fix ICE in macro import error recovery 2018-10-30 00:21:39 +03:00
Supress unhelpful diagnostics for unresolved top level attributes 2024-01-27 19:09:55 +08:00			`error: aborting due to 2 previous errors`
resolve: Fix ICE in macro import error recovery 2018-10-30 00:21:39 +03:00
			For more information about this error, try `rustc --explain E0432`.