rust/src/test/ui/issues/issue-32655.stderr

error: cannot find attribute `derive_Clone` in this scope
  --> $DIR/issue-32655.rs:3:11
   |
LL |         #[derive_Clone]
   |           ^^^^^^^^^^^^ help: an attribute macro with a similar name exists: `derive_const`
...
LL | foo!();
   | ------ in this macro invocation
   |
  ::: $SRC_DIR/core/src/macros/mod.rs:LL:COL
   |
LL |     pub macro derive_const($item:item) {
   |     ---------------------- similarly named attribute macro `derive_const` defined here
   |
   = note: this error originates in the macro `foo` (in Nightly builds, run with -Z macro-backtrace for more info)

error: cannot find attribute `derive_Clone` in this scope
  --> $DIR/issue-32655.rs:15:7
   |
LL |     #[derive_Clone]
   |       ^^^^^^^^^^^^ help: an attribute macro with a similar name exists: `derive_const`
   |
  ::: $SRC_DIR/core/src/macros/mod.rs:LL:COL
   |
LL |     pub macro derive_const($item:item) {
   |     ---------------------- similarly named attribute macro `derive_const` defined here

error: aborting due to 2 previous errors
resolve: Tweak "cannot find" wording for attributes 2019-09-15 09:55:18 +00:00			error: cannot find attribute `derive_Clone` in this scope
resolve: Use `feature(custom_attribute)` fallback only if the feature is enabled Normally `#![feature(...)]` shouldn't change behavior, but custom attributes in particular are in the process of retirement, and we should not produce a message telling to enable them. It also helps with unifying diagnostics for unresolved macros. 2019-07-11 22:00:20 +00:00			`--> $DIR/issue-32655.rs:3:11`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| #[derive_Clone]`
Add the `#[derive_const]` attribute 2022-09-20 11:55:07 +00:00			\| ^^^^^^^^^^^^ help: an attribute macro with a similar name exists: `derive_const`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`...`
			`LL \| foo!();`
Bless tests 2021-10-14 18:28:28 +00:00			`\| ------ in this macro invocation`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 13:56:47 +00:00			`\|`
Add the `#[derive_const]` attribute 2022-09-20 11:55:07 +00:00			`::: $SRC_DIR/core/src/macros/mod.rs:LL:COL`
			`\|`
			`LL \| pub macro derive_const($item:item) {`
			\| ---------------------- similarly named attribute macro `derive_const` defined here
			`\|`
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 19:52:25 +00:00			= note: this error originates in the macro `foo` (in Nightly builds, run with -Z macro-backtrace for more info)
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00
resolve: Tweak "cannot find" wording for attributes 2019-09-15 09:55:18 +00:00			error: cannot find attribute `derive_Clone` in this scope
resolve: Use `feature(custom_attribute)` fallback only if the feature is enabled Normally `#![feature(...)]` shouldn't change behavior, but custom attributes in particular are in the process of retirement, and we should not produce a message telling to enable them. It also helps with unifying diagnostics for unresolved macros. 2019-07-11 22:00:20 +00:00			`--> $DIR/issue-32655.rs:15:7`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| #[derive_Clone]`
Add the `#[derive_const]` attribute 2022-09-20 11:55:07 +00:00			\| ^^^^^^^^^^^^ help: an attribute macro with a similar name exists: `derive_const`
			`\|`
			`::: $SRC_DIR/core/src/macros/mod.rs:LL:COL`
			`\|`
			`LL \| pub macro derive_const($item:item) {`
			\| ---------------------- similarly named attribute macro `derive_const` defined here
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00
			`error: aborting due to 2 previous errors`