rust/tests/rustdoc-ui/ice-unresolved-import-100241.stderr

error[E0432]: unresolved import `inner`
  --> $DIR/ice-unresolved-import-100241.rs:9:13
   |
LL |     pub use inner::S;
   |             ^^^^^ you might be missing crate `inner`
   |
help: consider importing the `inner` crate
   |
LL + extern crate inner;
   |

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0432`.
Fix associated item removal suggestion We were previously telling people to write what was already there, instead of removal. ``` error[E0229]: associated item constraints are not allowed here --> $DIR/E0229.rs:13:25 \| LL \| fn baz<I>(x: &<I as Foo<A = Bar>>::A) {} \| ^^^^^^^ associated item constraint not allowed here \| help: consider removing this associated item binding \| LL - fn baz<I>(x: &<I as Foo<A = Bar>>::A) {} LL + fn baz<I>(x: &<I as Foo>::A) {} \| ``` 2024-07-09 22:11:20 +00:00			error[E0432]: unresolved import `inner`
			`--> $DIR/ice-unresolved-import-100241.rs:9:13`
			`\|`
			`LL \| pub use inner::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 `inner`
Fix associated item removal suggestion We were previously telling people to write what was already there, instead of removal. ``` error[E0229]: associated item constraints are not allowed here --> $DIR/E0229.rs:13:25 \| LL \| fn baz<I>(x: &<I as Foo<A = Bar>>::A) {} \| ^^^^^^^ associated item constraint not allowed here \| help: consider removing this associated item binding \| LL - fn baz<I>(x: &<I as Foo<A = Bar>>::A) {} LL + fn baz<I>(x: &<I as Foo>::A) {} \| ``` 2024-07-09 22:11:20 +00: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 `inner` crate
			`\|`
			`LL + extern crate inner;`
			`\|`
Fix associated item removal suggestion We were previously telling people to write what was already there, instead of removal. ``` error[E0229]: associated item constraints are not allowed here --> $DIR/E0229.rs:13:25 \| LL \| fn baz<I>(x: &<I as Foo<A = Bar>>::A) {} \| ^^^^^^^ associated item constraint not allowed here \| help: consider removing this associated item binding \| LL - fn baz<I>(x: &<I as Foo<A = Bar>>::A) {} LL + fn baz<I>(x: &<I as Foo>::A) {} \| ``` 2024-07-09 22:11:20 +00:00
			`error: aborting due to 1 previous error`

			For more information about this error, try `rustc --explain E0432`.