rust/tests/ui/macros/issue-5060.rs

// run-pass
macro_rules! print_hd_tl {
    ($field_hd:ident, $($field_tl:ident),+) => ({
        print!("{}", stringify!($field_hd));
        print!("::[");
        $(
            print!("{}", stringify!($field_tl));
            print!(", ");
        )+
        print!("]\n");
    })
}

pub fn main() {
    print_hd_tl!(x, y, z, w)
}
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! print_hd_tl {`
testsuite: Add test cases, some xfailed Closes #5060 Closes #4446 Closes #5192 2013-06-27 16:53:40 -07:00			`($field_hd:ident, $($field_tl:ident),+) => ({`
Remove re-exports of std::io::stdio::{print, println} in the prelude. The `print!` and `println!` macros are now the preferred method of printing, and so there is no reason to export the `stdio` functions in the prelude. The functions have also been replaced by their macro counterparts in the tutorial and other documentation so that newcomers don't get confused about what they should be using. 2014-01-09 21:06:55 +11:00			`print!("{}", stringify!($field_hd));`
			`print!("::[");`
testsuite: Add test cases, some xfailed Closes #5060 Closes #4446 Closes #5192 2013-06-27 16:53:40 -07:00			`$(`
Remove re-exports of std::io::stdio::{print, println} in the prelude. The `print!` and `println!` macros are now the preferred method of printing, and so there is no reason to export the `stdio` functions in the prelude. The functions have also been replaced by their macro counterparts in the tutorial and other documentation so that newcomers don't get confused about what they should be using. 2014-01-09 21:06:55 +11:00			`print!("{}", stringify!($field_tl));`
			`print!(", ");`
testsuite: Add test cases, some xfailed Closes #5060 Closes #4446 Closes #5192 2013-06-27 16:53:40 -07:00			`)+`
Miscellaneous cleanup for old issues. 2015-09-20 11:35:08 +01:00			`print!("]\n");`
testsuite: Add test cases, some xfailed Closes #5060 Closes #4446 Closes #5192 2013-06-27 16:53:40 -07:00			`})`
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			`}`
testsuite: Add test cases, some xfailed Closes #5060 Closes #4446 Closes #5192 2013-06-27 16:53:40 -07:00
Fix run-pass tests to have 'pub fn main' This is required by the check-fast target because each test is slurped up into a submodule. 2013-09-25 00:43:37 -07:00			`pub fn main() {`
testsuite: Add test cases, some xfailed Closes #5060 Closes #4446 Closes #5192 2013-06-27 16:53:40 -07:00			`print_hd_tl!(x, y, z, w)`
			`}`