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.
9 lines
274 B
Rust
9 lines
274 B
Rust
#![feature(stmt_expr_attributes)]
|
|
|
|
#[foo] //~ ERROR cannot find attribute macro `foo` in this scope
|
|
fn main() {
|
|
#[foo] //~ ERROR cannot find attribute macro `foo` in this scope
|
|
let x = ();
|
|
#[foo] //~ ERROR cannot find attribute macro `foo` in this scope
|
|
x
|
|
}
|