rust/tests/ui/macros/macro-outer-attributes.stderr

error[E0425]: cannot find function `bar` in module `a`
  --> $DIR/macro-outer-attributes.rs:18:8
   |
LL |     a::bar();
   |        ^^^ not found in `a`
   |
note: found an item that was configured out
  --> $DIR/macro-outer-attributes.rs:9:14
   |
LL |       pub fn bar() { });
   |              ^^^
help: consider importing this function
   |
LL + use b::bar;
   |
help: if you import `bar`, refer to it directly
   |
LL -     a::bar();
LL +     bar();
   |

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0425`.
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			error[E0425]: cannot find function `bar` in module `a`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/macro-outer-attributes.rs:18:8`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| a::bar();`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			\| ^^^ not found in `a`
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages. 2019-10-24 00:20:58 -05:00			`\|`
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			`note: found an item that was configured out`
			`--> $DIR/macro-outer-attributes.rs:9:14`
			`\|`
			`LL \| pub fn bar() { });`
			`\| ^^^`
Tweak wording 2022-05-02 21:07:47 -05:00			`help: consider importing this function`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Tweak output for 'add line' suggestion 2023-03-17 21:18:39 -05:00			`LL + use b::bar;`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Tweak wording 2022-05-02 21:07:47 -05:00			help: if you import `bar`, refer to it directly
When suggesting to import an item, also suggest changing the path if appropriate When we don't find an item we search all of them for an appropriate import and suggest `use`ing it. This is sometimes done for expressions that have paths with more than one segment. We now also suggest changing that path to work with the `use`. Fix #95413 2022-04-23 18:41:36 -05:00			`\|`
			`LL - a::bar();`
			`LL + bar();`
diagnostics: fix trailing space 2022-06-08 12:34:57 -05:00			`\|`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
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`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
			For more information about this error, try `rustc --explain E0425`.