rust/tests/ui/macros/macro-invocation-with-variable-in-scope-9737.rs

// https://github.com/rust-lang/rust/issues/9737
//@ run-pass
#![allow(unused_variables)]
macro_rules! f {
    (v: $x:expr) => ( println!("{}", $x) )
}

fn main () {
    let v = 5;
    f!(v: 3);
}
Rehome tests/ui/issues/ tests [4/?] 2025-07-13 16:39:45 -04:00			`// https://github.com/rust-lang/rust/issues/9737`
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 14:18:55 +02:00			`//@ run-pass`
Add `#![allow(..)]` as necessary to get re-migrated run-pass tests compiling with clean stderr again. Most were added mechanically. 2018-09-25 23:51:35 +02:00			`#![allow(unused_variables)]`
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! f {`
			`(v: $x:expr) => ( println!("{}", $x) )`
			`}`
added xfailed test for issue 9737 2013-11-22 13:43:22 -08:00
			`fn main () {`
			`let v = 5;`
			`f!(v: 3);`
			`}`