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.
14 lines
305 B
Rust
14 lines
305 B
Rust
// Check that unknown attribute error is shown even if there are unresolved macros.
|
|
|
|
#[marco_use] // typo
|
|
//~^ ERROR cannot find attribute macro `marco_use` in this scope
|
|
mod foo {
|
|
macro_rules! bar {
|
|
() => ();
|
|
}
|
|
}
|
|
|
|
fn main() {
|
|
bar!(); //~ ERROR cannot find macro `bar!` in this scope
|
|
}
|