rust/tests/ui/macros/macro-stmt_macro_in_expr_macro.rs

// run-pass
#![allow(dead_code)]
macro_rules! foo {
    () => {
        struct Bar;
        struct Baz;
    }
}

macro_rules! grault {
    () => {{
        foo!();
        struct Xyzzy;
        0
    }}
}

fn main() {
    let x = grault!();
    assert_eq!(x, 0);
}
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(dead_code)]`
Improves handling of statement macros. Statement macros are now treated somewhat like item macros, in that a statement macro can now expand into a series of statements, rather than just a single statement. This allows statement macros to be nested inside other kinds of macros and expand properly, where previously the expansion would only work when no nesting was present. See: src/test/run-pass/macro-stmt_macro_in_expr_macro.rs src/test/run-pass/macro-nested_stmt_macro.rs This changes the interface of the MacResult trait. make_stmt has become make_stmts and now returns a vector, rather than a single item. Plugin writers who were implementing MacResult will have breakage, as well as anyone using MacEager::stmt. See: src/libsyntax/ext/base.rs This also causes a minor difference in behavior to the diagnostics produced by certain malformed macros. See: src/test/compile-fail/macro-incomplete-parse.rs 2015-04-07 08:21:18 -05:00			`macro_rules! foo {`
			`() => {`
			`struct Bar;`
			`struct Baz;`
			`}`
			`}`

			`macro_rules! grault {`
			`() => {{`
			`foo!();`
			`struct Xyzzy;`
			`0`
			`}}`
			`}`

			`fn main() {`
			`let x = grault!();`
			`assert_eq!(x, 0);`
			`}`