rust/tests/ui/macros/macro-outer-attributes.rs

#![feature(rustc_attrs)]

macro_rules! test { ($nm:ident,
                     #[$a:meta],
                     $i:item) => (mod $nm { #[$a] $i }); }

test!(a,
      #[cfg(qux)],
      pub fn bar() { });

test!(b,
      #[cfg(not(qux))],
      pub fn bar() { });

// test1!(#[bar])
#[rustc_dummy]
fn main() {
    a::bar(); //~ ERROR cannot find function `bar` in module `a`
    b::bar();
}
Introduce `#[rustc_dummy]` attribute and use it in tests Unlike other built-in attributes, this attribute accepts any input 2019-06-08 11:36:43 +03:00			`#![feature(rustc_attrs)]`
Add custom_attribute gate to tests which need them 2015-02-14 16:15:43 +05:30
Modernize macro_rules! invocations macro_rules! is like an item that defines a macro. Other items don't have a trailing semicolon, or use a paren-delimited body. If there's an argument for matching the invocation syntax, e.g. parentheses for an expr macro, then I think that applies more strongly to the inner delimiters on the LHS, wrapping the individual argument patterns. 2015-01-02 14:44:21 -08:00			`macro_rules! test { ($nm:ident,`
syntax: Accept meta matchers in macros This removes the `attr` matcher and adds a `meta` matcher. The previous `attr` matcher is now ambiguous because it doesn't disambiguate whether it means inner attribute or outer attribute. The new behavior can still be achieved by taking an argument of the form `#[$foo:meta]` (the brackets are part of the macro pattern). Closes #13067 2014-03-26 16:14:07 -07:00			`#[$a:meta],`
Modernize macro_rules! invocations macro_rules! is like an item that defines a macro. Other items don't have a trailing semicolon, or use a paren-delimited body. If there's an argument for matching the invocation syntax, e.g. parentheses for an expr macro, then I think that applies more strongly to the inner delimiters on the LHS, wrapping the individual argument patterns. 2015-01-02 14:44:21 -08:00			`$i:item) => (mod $nm { #[$a] $i }); }`
Allow attributes to appear as macro arguments Fixes #8393 2013-08-08 13:28:06 -04:00
			`test!(a,`
			`#[cfg(qux)],`
librustc: Always parse `macro!()`/`macro![]` as expressions if not followed by a semicolon. This allows code like `vec![1i, 2, 3].len();` to work. This breaks code that uses macros as statements without putting semicolons after them, such as: fn main() { ... assert!(a == b) assert!(c == d) println(...); } It also breaks code that uses macros as items without semicolons: local_data_key!(foo) fn main() { println("hello world") } Add semicolons to fix this code. Those two examples can be fixed as follows: fn main() { ... assert!(a == b); assert!(c == d); println(...); } local_data_key!(foo); fn main() { println("hello world") } RFC #378. Closes #18635. [breaking-change] 2014-11-14 09:18:10 -08:00			`pub fn bar() { });`
Allow attributes to appear as macro arguments Fixes #8393 2013-08-08 13:28:06 -04:00
			`test!(b,`
			`#[cfg(not(qux))],`
librustc: Always parse `macro!()`/`macro![]` as expressions if not followed by a semicolon. This allows code like `vec![1i, 2, 3].len();` to work. This breaks code that uses macros as statements without putting semicolons after them, such as: fn main() { ... assert!(a == b) assert!(c == d) println(...); } It also breaks code that uses macros as items without semicolons: local_data_key!(foo) fn main() { println("hello world") } Add semicolons to fix this code. Those two examples can be fixed as follows: fn main() { ... assert!(a == b); assert!(c == d); println(...); } local_data_key!(foo); fn main() { println("hello world") } RFC #378. Closes #18635. [breaking-change] 2014-11-14 09:18:10 -08:00			`pub fn bar() { });`
Allow attributes to appear as macro arguments Fixes #8393 2013-08-08 13:28:06 -04:00
			`// test1!(#[bar])`
Introduce `#[rustc_dummy]` attribute and use it in tests Unlike other built-in attributes, this attribute accepts any input 2019-06-08 11:36:43 +03:00			`#[rustc_dummy]`
Allow attributes to appear as macro arguments Fixes #8393 2013-08-08 13:28:06 -04:00			`fn main() {`
resolve: Do not use "resolve"/"resolution" in error messages 2017-01-12 01:18:08 +03:00			a::bar(); //~ ERROR cannot find function `bar` in module `a`
Allow attributes to appear as macro arguments Fixes #8393 2013-08-08 13:28:06 -04:00			`b::bar();`
			`}`