rust/tests/ui/binding/match-var-hygiene.rs

// run-pass
// shouldn't affect evaluation of $ex.
macro_rules! bad_macro { ($ex:expr) => (
    {match 9 {_x => $ex}}
)}

fn main() {
    match 8 {
        _x => assert_eq!(bad_macro!(_x),8)
    }
}
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 07:18:55 -05:00			`// run-pass`
added xfailed tests for two other flavors of var hygiene 2013-09-21 01:37:19 -05:00			`// shouldn't affect evaluation of $ex.`
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 16:44:21 -06:00			`macro_rules! bad_macro { ($ex:expr) => (`
added xfailed tests for two other flavors of var hygiene 2013-09-21 01:37:19 -05:00			`{match 9 {_x => $ex}}`
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 16:44:21 -06:00			`)}`
added xfailed tests for two other flavors of var hygiene 2013-09-21 01:37:19 -05:00
			`fn main() {`
			`match 8 {`
			`_x => assert_eq!(bad_macro!(_x),8)`
			`}`
			`}`