rust/tests/rustdoc-ui/intra-doc/unresolved-import-recovery.stderr

error[E0433]: failed to resolve: you might be missing crate `unresolved_crate`
  --> $DIR/unresolved-import-recovery.rs:3:5
   |
LL | use unresolved_crate::module::Name;
   |     ^^^^^^^^^^^^^^^^ you might be missing crate `unresolved_crate`
   |
help: consider importing the `unresolved_crate` crate
   |
LL + extern crate unresolved_crate;
   |

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0433`.
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 14:43:46 -05:00			error[E0433]: failed to resolve: you might be missing crate `unresolved_crate`
resolve: Create dummy bindings for all unresolved imports 2022-04-10 09:21:58 -05:00			`--> $DIR/unresolved-import-recovery.rs:3:5`
			`\|`
			`LL \| use unresolved_crate::module::Name;`
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 14:43:46 -05:00			\| ^^^^^^^^^^^^^^^^ you might be missing crate `unresolved_crate`
suggest `extern crate foo` when failing to resolve `use foo` fix ci error 2022-05-21 21:48:35 -05: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 14:31:02 -05:00			help: consider importing the `unresolved_crate` crate
			`\|`
			`LL + extern crate unresolved_crate;`
			`\|`
resolve: Create dummy bindings for all unresolved imports 2022-04-10 09:21:58 -05:00
Bless rustdoc-ui tests Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 10:44:51 -06:00			`error: aborting due to 1 previous error`
resolve: Create dummy bindings for all unresolved imports 2022-04-10 09:21:58 -05:00
			For more information about this error, try `rustc --explain E0433`.