rust/tests/ui/conditional-compilation/cfg-attr-unknown-attribute-macro-expansion.rs

macro_rules! foo {
    () => {
        #[cfg_attr(all(), unknown)]
        //~^ ERROR cannot find attribute `unknown` in this scope
        fn foo() {}
    }
}

foo!();

fn main() {}
Run feature-gating on the final AST passed to the compiler. This ensures we catch everything; previously, an unknown attribute inserted by #[cfg_attr(...)] in a macro expansion would not be detected. 2015-03-04 18:05:38 +11:00			`macro_rules! foo {`
			`() => {`
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-12 01:00:20 +03:00			`#[cfg_attr(all(), unknown)]`
resolve: Tweak "cannot find" wording for attributes 2019-09-15 12:55:18 +03:00			//~^ ERROR cannot find attribute `unknown` in this scope
Run feature-gating on the final AST passed to the compiler. This ensures we catch everything; previously, an unknown attribute inserted by #[cfg_attr(...)] in a macro expansion would not be detected. 2015-03-04 18:05:38 +11:00			`fn foo() {}`
			`}`
			`}`

			`foo!();`

			`fn main() {}`