Misalignment with `or` pattern arguments.

[fbernier]

The following code:

fn is_meta_character(c: char) -> bool {
    matches!(
        c,
        '\\' | '.' | '+' | '(' | ')' | '|' | '[' | ']' | '{' | '}' | '^' |
        '$'  | '#' | '&' | '-' | '~' | '*' | '?'
    )
}

gets formatted into

fn is_meta_character(c: char) -> bool {
    matches!(
        c,
        '\\' | '.'
            | '+'
            | '('
            | ')'
            | '|'
            | '['
            | ']'
            | '{'
            | '}'
            | '^'
            | '$'
            | '#'
            | '&'
            | '-'
            | '~'
            | '*'
            | '?'
    )
}

I see two issues with this. First, horizontal bars are misaligned, and second it's a big waste of vertical space. I did not have time to gather more info as of now but will update this issue if I get back to it.

Thanks!

[calebcartwright]

Thank you for reaching out, but I'm going to close as a duplicate of #4462

Few things to be aware of in this context:

• rustfmt has fairly limited support for formatting macros (refs format macros #8)
• When rustfmt encounters macro calls with certain delimiters it will check to see if the inputs can be parsed as valid rust code, and if so then the code is formatted according to the corresponding prescription from the Rust Style Guide
• matches! calls are currently treated like any other macro call, and since the second arg gets parsed as a binop expression it is formatted accordingly
• In rare, well known cases, we can add some special case handling for certain macro calls, and ultimately plan to do the same for matches one day too