rust/tests/ui/deriving/deriving-in-macro.rs

// run-pass
// pretty-expanded FIXME #23616
#![allow(non_camel_case_types)]

macro_rules! define_vec {
    () => (
        mod foo {
            #[derive(PartialEq)]
            pub struct bar;
        }
    )
}

define_vec![];

pub fn main() {}
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`
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 15:13:15 -05:00			`// pretty-expanded FIXME #23616`
Add `#![allow(..)]` for a slew of lints of migrated run-pass tests, to silence stderr output. 2018-08-31 08:02:01 -05:00			`#![allow(non_camel_case_types)]`
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 15:13:15 -05: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 16:44:21 -06:00			`macro_rules! define_vec {`
Add a test for #6976 Closes #6976 2013-11-16 00:34:52 -06:00			`() => (`
			`mod foo {`
Use `derive` rather than `deriving` in tests 2014-12-30 22:32:49 -06:00			`#[derive(PartialEq)]`
Add a test for #6976 Closes #6976 2013-11-16 00:34:52 -06:00			`pub struct bar;`
			`}`
			`)`
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			`}`
Add a test for #6976 Closes #6976 2013-11-16 00:34:52 -06:00
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 16:54:04 -05:00			`define_vec![];`
Add a test for #6976 Closes #6976 2013-11-16 00:34:52 -06:00
			`pub fn main() {}`