rust/tests/ui/attributes/field-attributes-vis-unresolved.stderr

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `nonexistent`
  --> $DIR/field-attributes-vis-unresolved.rs:17:12
   |
LL |     pub(in nonexistent) field: u8
   |            ^^^^^^^^^^^ use of unresolved module or unlinked crate `nonexistent`
   |
help: you might be missing a crate named `nonexistent`, add it to your project and import it in your code
   |
LL + extern crate nonexistent;
   |

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `nonexistent`
  --> $DIR/field-attributes-vis-unresolved.rs:22:12
   |
LL |     pub(in nonexistent) u8
   |            ^^^^^^^^^^^ use of unresolved module or unlinked crate `nonexistent`
   |
help: you might be missing a crate named `nonexistent`, add it to your project and import it in your code
   |
LL + extern crate nonexistent;
   |

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0433`.
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			error[E0433]: failed to resolve: use of unresolved module or unlinked crate `nonexistent`
resolve: Resolve visibilities on fields with non-builtin attributes 2019-12-06 21:03:58 +00:00			`--> $DIR/field-attributes-vis-unresolved.rs:17:12`
			`\|`
			`LL \| pub(in nonexistent) field: u8`
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			\| ^^^^^^^^^^^ use of unresolved module or unlinked crate `nonexistent`
suggest `extern crate foo` when failing to resolve `use foo` fix ci error 2022-05-22 02:48:35 +00:00			`\|`
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			help: you might be missing a crate named `nonexistent`, add it to your project and import it in your code
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			`\|`
			`LL + extern crate nonexistent;`
			`\|`
resolve: Resolve visibilities on fields with non-builtin attributes 2019-12-06 21:03:58 +00:00
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			error[E0433]: failed to resolve: use of unresolved module or unlinked crate `nonexistent`
resolve: Resolve visibilities on fields with non-builtin attributes 2019-12-06 21:03:58 +00:00			`--> $DIR/field-attributes-vis-unresolved.rs:22:12`
			`\|`
			`LL \| pub(in nonexistent) u8`
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			\| ^^^^^^^^^^^ use of unresolved module or unlinked crate `nonexistent`
suggest `extern crate foo` when failing to resolve `use foo` fix ci error 2022-05-22 02:48:35 +00:00			`\|`
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			help: you might be missing a crate named `nonexistent`, add it to your project and import it in your code
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			`\|`
			`LL + extern crate nonexistent;`
			`\|`
resolve: Resolve visibilities on fields with non-builtin attributes 2019-12-06 21:03:58 +00:00
resolve: Make visibility resolution more speculative To avoid potential duplicate diagnostics and separate the error reporting logic 2019-12-06 22:49:21 +00:00			`error: aborting due to 2 previous errors`
resolve: Resolve visibilities on fields with non-builtin attributes 2019-12-06 21:03:58 +00:00
resolve: Make visibility resolution more speculative To avoid potential duplicate diagnostics and separate the error reporting logic 2019-12-06 22:49:21 +00:00			For more information about this error, try `rustc --explain E0433`.