os-rust/tests/ui/resolve/resolve-bad-visibility.stderr
Esteban Küber 850faea030 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-24 21:03:27 +00:00

38 lines
1.2 KiB
Text

error[E0577]: expected module, found enum `E`
--> $DIR/resolve-bad-visibility.rs:4:8
|
LL | pub(in E) struct S;
| ^ not a module
error[E0577]: expected module, found trait `Tr`
--> $DIR/resolve-bad-visibility.rs:5:8
|
LL | pub(in Tr) struct Z;
| ^^ not a module
error[E0742]: visibilities can only be restricted to ancestor modules
--> $DIR/resolve-bad-visibility.rs:6:8
|
LL | pub(in std::vec) struct F;
| ^^^^^^^^
error[E0433]: failed to resolve: you might be missing crate `nonexistent`
--> $DIR/resolve-bad-visibility.rs:7:8
|
LL | pub(in nonexistent) struct G;
| ^^^^^^^^^^^ you might be missing crate `nonexistent`
|
= help: consider adding `extern crate nonexistent` to use the `nonexistent` crate
error[E0433]: failed to resolve: you might be missing crate `too_soon`
--> $DIR/resolve-bad-visibility.rs:8:8
|
LL | pub(in too_soon) struct H;
| ^^^^^^^^ you might be missing crate `too_soon`
|
= help: consider adding `extern crate too_soon` to use the `too_soon` crate
error: aborting due to 5 previous errors
Some errors have detailed explanations: E0433, E0577, E0742.
For more information about an error, try `rustc --explain E0433`.