79f0d88de8
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.
21 lines
415 B
Plaintext
21 lines
415 B
Plaintext
error: cannot find attribute macro `foo` in this scope
|
|
--> $DIR/custom_attribute.rs:3:3
|
|
|
|
|
LL | #[foo]
|
|
| ^^^
|
|
|
|
error: cannot find attribute macro `foo` in this scope
|
|
--> $DIR/custom_attribute.rs:5:7
|
|
|
|
|
LL | #[foo]
|
|
| ^^^
|
|
|
|
error: cannot find attribute macro `foo` in this scope
|
|
--> $DIR/custom_attribute.rs:7:7
|
|
|
|
|
LL | #[foo]
|
|
| ^^^
|
|
|
|
error: aborting due to 3 previous errors
|
|
|