rust/tests/ui/macros/for-loop-macro-rules-hygiene.rs

//! Regression test for https://github.com/rust-lang/rust/issues/15189

//@ run-pass
macro_rules! third {
    ($e:expr) => ({let x = 2; $e[x]})
}

fn main() {
    let x = vec![10_usize,11_usize,12_usize,13_usize];
    let t = third!(x);
    assert_eq!(t,12_usize);
}
comments 2025-07-24 19:07:20 +05:00			`//! Regression test for https://github.com/rust-lang/rust/issues/15189`

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`
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! third {`
			`($e:expr) => ({let x = 2; $e[x]})`
			`}`
work around 15189 in test cases 2014-06-25 17:08:08 -07:00
			`fn main() {`
Changed most vec! invocations to use square braces Most of the Rust community agrees that the vec! macro is clearer when called using square brackets [] instead of regular brackets (). Most of these ocurrences are from before macros allowed using different types of brackets. There is one left unchanged in a pretty-print test, as the pretty printer still wants it to have regular brackets. 2016-10-29 22:54:04 +01:00			`let x = vec![10_usize,11_usize,12_usize,13_usize];`
work around 15189 in test cases 2014-06-25 17:08:08 -07:00			`let t = third!(x);`
Update suffixes en masse in tests using `perl -p -i -e` 2015-02-18 05:42:01 -05:00			`assert_eq!(t,12_usize);`
work around 15189 in test cases 2014-06-25 17:08:08 -07:00			`}`