os-rust/tests/ui/imports/issue-1697.rs

// Testing that we don't fail abnormally after hitting the errors

use unresolved::*;
//~^ ERROR unresolved import `unresolved` [E0432]
//~| NOTE you might be missing crate `unresolved`
//~| HELP consider importing the `unresolved` crate

fn main() {}
test: Add a test for #1697 2012-02-22 21:14:27 -08:00			`// Testing that we don't fail abnormally after hitting the errors`

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			`use unresolved::*;`
			//~^ ERROR unresolved import `unresolved` [E0432]
			//~\| NOTE you might be missing crate `unresolved`
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
test: Add a test for #1697 2012-02-22 21:14:27 -08:00
rustc: reduce redundant resolve errors. 2014-06-05 22:37:52 +01:00			`fn main() {}`