mathieu/os-rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
os-rust/tests/ui/resolve/extern-prelude-fail.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

27 lines
799 B
Text
Raw Permalink Normal View History

Move one test from run-make-fulldeps to ui
2019-03-21 23:36:50 +03:00
error[E0432]: unresolved import `extern_prelude`
--> $DIR/extern-prelude-fail.rs:7:9
|
LL | use extern_prelude::S;
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 `extern_prelude`
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 `extern_prelude` crate
|
LL + extern crate extern_prelude;
|
Move one test from run-make-fulldeps to ui
2019-03-21 23:36:50 +03:00
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
error[E0433]: failed to resolve: you might be missing crate `extern_prelude`
Move one test from run-make-fulldeps to ui
2019-03-21 23:36:50 +03:00
--> $DIR/extern-prelude-fail.rs:8:15
|
LL | let s = ::extern_prelude::S;
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 `extern_prelude`
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 `extern_prelude` crate
|
LL + extern crate extern_prelude;
|
Move one test from run-make-fulldeps to ui
2019-03-21 23:36:50 +03:00
error: aborting due to 2 previous errors
hide `--explain` hint if error has no extended info
2019-04-17 13:26:38 -04:00
Some errors have detailed explanations: E0432, E0433.
Move one test from run-make-fulldeps to ui
2019-03-21 23:36:50 +03:00
For more information about an error, try `rustc --explain E0432`.
Reference in a new issue Copy permalink