rustfmt thinks that a pattern matching is a closure

When formatting this code:

fn is_something(foo: Foo, bar: Bar) -> bool {
    matches!((legacy_required_finality, signature_weight),
        | (LegacyRequiredFinality::Any, Insufficient | Weak | Strict)
        | (LegacyRequiredFinality::Weak, Weak | Strict)
        | (LegacyRequiredFinality::Strict, Strict)
    )
}

It is written like that:

fn is_something(foo: Foo, bar: Bar) -> bool {
    matches!((legacy_required_finality, signature_weight), |(
        LegacyRequiredFinality::Any,
        Insufficient | Weak | Strict,
    )| (
        LegacyRequiredFinality::Weak,
        Weak | Strict
    ) | (
        LegacyRequiredFinality::Strict,
        Strict
    ))
}

I think that rustfmt sees it as a closure.

I tried to reproduce with a simpler example, but it doesn't work. I think it comes from diverse things, like the fact there is a tuple.

No source file or test is named. Start by running rustfmt on the two Rust snippets from the issue and compare the formatting, then trace the handling of the matches! macro's tuple patterns and closure-like syntax; done means the pattern is formatted as shown in the first snippet without regressing related formatting.