rust/tests/ui/parser/macro/issue-37234.rs

macro_rules! failed {
    () => {{
        let x = 5 ""; //~ ERROR found `""`
    }}
}

fn main() {
    failed!();
}
Don't spin expanding stmt macros. If we can't make progress when parsing a macro expansion as a statement then we should just bail. This alleviates the symptoms shown in e.g. #37113 but it doesn't fix the problem that parsing invalid enum bodies (and others) leaves the parser in a crappy state. 2016-10-17 23:01:36 -05:00			`macro_rules! failed {`
			`() => {{`
			let x = 5 ""; //~ ERROR found `""`
Consume trailing doc comments to avoid parse errors 2017-11-24 09:34:24 -06:00			`}}`
Don't spin expanding stmt macros. If we can't make progress when parsing a macro expansion as a statement then we should just bail. This alleviates the symptoms shown in e.g. #37113 but it doesn't fix the problem that parsing invalid enum bodies (and others) leaves the parser in a crappy state. 2016-10-17 23:01:36 -05:00			`}`

			`fn main() {`
			`failed!();`
			`}`