rust/tests/ui/conditional-compilation/cfg-attr-unknown-attribute-macro-expansion.stderr

error: cannot find attribute `unknown` in this scope
  --> $DIR/cfg-attr-unknown-attribute-macro-expansion.rs:3:27
   |
LL |         #[cfg_attr(all(), unknown)]
   |                           ^^^^^^^
...
LL | foo!();
   | ------ in this macro invocation
   |
   = note: this error originates in the macro `foo` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error
resolve: Tweak "cannot find" wording for attributes 2019-09-15 12:55:18 +03:00			error: cannot find attribute `unknown` in this scope
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/cfg-attr-unknown-attribute-macro-expansion.rs:3:27`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| #[cfg_attr(all(), unknown)]`
resolve: Consolidate error reporting for resolved macros in `fn resolve_macro_to_def` 2018-08-15 03:51:12 +03:00			`\| ^^^^^^^`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			`...`
			`LL \| foo!();`
Bless tests 2021-10-14 13:28:28 -05:00			`\| ------ in this macro invocation`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 15:56:47 +02:00			`\|`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. 2021-02-13 14:52:25 -05:00			= note: this error originates in the macro `foo` (in Nightly builds, run with -Z macro-backtrace for more info)
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00
			`error: aborting due to previous error`