rust/tests/target/configs/match_arm_blocks/true.rs

// rustfmt-match_arm_blocks: true
// Wrap match-arms

fn main() {
    match lorem {
        true => {
            foooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo(x)
        }
        false => {
            println!("{}", sit)
        }
    }
}
Rename wrap_match_arms to match_arm_blocks 2017-11-26 22:35:27 -06:00			`// rustfmt-match_arm_blocks: true`
Add source/target tests for each config option 2017-04-30 16:49:39 -05:00			`// Wrap match-arms`

			`fn main() {`
			`match lorem {`
			`true => {`
Update wrap_match_arms option tests and visual guide 2017-07-11 07:53:57 -05:00			`foooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo(x)`
Add source/target tests for each config option 2017-04-30 16:49:39 -05:00			`}`
Don't flatten a block containing a single macro call We no longer flatten a block that looks like this: ```rust match val { pat => { macro_call!() } } ``` Currently, rust ignores trailing semicolons in macro expansion in expression position (see https://github.com/rust-lang/rust/issues/33953) If this is changed, flattening a block with a macro call may break the user's code - the trailing semicolon will no longer parse if the macro call occurs immediately on the right-hand side of the match arm (e.g. `pat => macro_call!()`) 2020-10-27 17:52:02 -05:00			`false => {`
			`println!("{}", sit)`
			`}`
Add source/target tests for each config option 2017-04-30 16:49:39 -05:00			`}`
			`}`