rust/tests/ui/cfg/diagnostics-not-a-def.stderr

error[E0425]: cannot find function `i_am_not` in module `inner`
  --> $DIR/diagnostics-not-a-def.rs:12:12
   |
LL |     inner::i_am_not();
   |            ^^^^^^^^ not found in `inner`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0425`.
Remember names of `cfg`-ed out items to mention them in diagnostics `#[cfg]`s are frequently used to gate crate content behind cargo features. This can lead to very confusing errors when features are missing. For example, `serde` doesn't have the `derive` feature by default. Therefore, `serde::Serialize` fails to resolve with a generic error, even though the macro is present in the docs. This commit adds a list of all stripped item names to metadata. This is filled during macro expansion and then, through a fed query, persisted in metadata. The downstream resolver can then access the metadata to look at possible candidates for mentioning in the errors. This slightly increases metadata (800k->809k for the feature-heavy windows crate), but not enough to really matter. 2023-03-10 15:39:14 -06:00			error[E0425]: cannot find function `i_am_not` in module `inner`
RFC 2383: Stabilize `lint_reasons` :tada: 2024-02-10 15:53:34 -06:00			`--> $DIR/diagnostics-not-a-def.rs:12:12`
Remember names of `cfg`-ed out items to mention them in diagnostics `#[cfg]`s are frequently used to gate crate content behind cargo features. This can lead to very confusing errors when features are missing. For example, `serde` doesn't have the `derive` feature by default. Therefore, `serde::Serialize` fails to resolve with a generic error, even though the macro is present in the docs. This commit adds a list of all stripped item names to metadata. This is filled during macro expansion and then, through a fed query, persisted in metadata. The downstream resolver can then access the metadata to look at possible candidates for mentioning in the errors. This slightly increases metadata (800k->809k for the feature-heavy windows crate), but not enough to really matter. 2023-03-10 15:39:14 -06:00			`\|`
			`LL \| inner::i_am_not();`
			\| ^^^^^^^^ not found in `inner`

Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Remember names of `cfg`-ed out items to mention them in diagnostics `#[cfg]`s are frequently used to gate crate content behind cargo features. This can lead to very confusing errors when features are missing. For example, `serde` doesn't have the `derive` feature by default. Therefore, `serde::Serialize` fails to resolve with a generic error, even though the macro is present in the docs. This commit adds a list of all stripped item names to metadata. This is filled during macro expansion and then, through a fed query, persisted in metadata. The downstream resolver can then access the metadata to look at possible candidates for mentioning in the errors. This slightly increases metadata (800k->809k for the feature-heavy windows crate), but not enough to really matter. 2023-03-10 15:39:14 -06:00
			For more information about this error, try `rustc --explain E0425`.