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 use of unresolved module or unlinked crate `unresolved`
//~| HELP you might be missing a crate named `unresolved`

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]
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			//~\| NOTE use of unresolved module or unlinked crate `unresolved`
			//~\| HELP you might be missing a crate named `unresolved`
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() {}`