rust/tests/ui/binding/match-in-macro.rs

// run-pass

enum Foo {
    B { b1: isize, bb1: isize},
}

macro_rules! match_inside_expansion {
    () => (
        match (Foo::B { b1:29 , bb1: 100}) {
            Foo::B { b1:b2 , bb1:bb2 } => b2+bb2
        }
    )
}

pub fn main() {
    assert_eq!(match_inside_expansion!(),129);
}
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`
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 13:13:15 -07:00
added run-pass test for issue #9049 2013-09-09 21:32:10 -07:00			`enum Foo {`
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 17:06:52 -07:00			`B { b1: isize, bb1: isize},`
added run-pass test for issue #9049 2013-09-09 21:32:10 -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			`macro_rules! match_inside_expansion {`
added run-pass test for issue #9049 2013-09-09 21:32:10 -07:00			`() => (`
Switch to purely namespaced enums This breaks code that referred to variant names in the same namespace as their enum. Reexport the variants in the old location or alter code to refer to the new locations: ``` pub enum Foo { A, B } fn main() { let a = A; } ``` => ``` pub use self::Foo::{A, B}; pub enum Foo { A, B } fn main() { let a = A; } ``` or ``` pub enum Foo { A, B } fn main() { let a = Foo::A; } ``` [breaking-change] 2014-11-06 00:05:53 -08:00			`match (Foo::B { b1:29 , bb1: 100}) {`
			`Foo::B { b1:b2 , bb1:bb2 } => b2+bb2`
added run-pass test for issue #9049 2013-09-09 21:32:10 -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			`}`
added run-pass test for issue #9049 2013-09-09 21:32:10 -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() {`
added run-pass test for issue #9049 2013-09-09 21:32:10 -07:00			`assert_eq!(match_inside_expansion!(),129);`
			`}`