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.
10 lines
166 B
Rust
10 lines
166 B
Rust
// gate-test-custom_inner_attributes
|
|
|
|
#![feature(custom_attribute)]
|
|
|
|
#[foo]
|
|
mod foo {
|
|
#![foo] //~ ERROR non-builtin inner attributes are unstable
|
|
}
|
|
|
|
fn main() {}
|