`map_flatten` could suggest `filter(matches!())` in case of `map( match { _ => Option }).flatten()`

[matthiaskrgr]

Description

I hope this not too convoluted 😅

I came across some code like

.iter()
        .map(|n| match n {
            0 | 2 | 5 => Some(n),
            _ => None,
        })
        .flatten()

clippy already recognizes the pattern and filter_map fires:

help: try replacing `map` with `filter_map` and remove the `.flatten()`
   |
6  ~         .filter_map(|n| match n {
7  +             0 | 2 | 5 => Some(n),
8  +             _ => None,
9  +         })

but, I believe it would be more elegant to completely forgo the "map" as well as the "match" by using filter(.. matches!()) in case we find ourselves matching on a pattern:

        .iter()
        .filter(|n| matches!(n, 0 | 2 | 5,))
        .collect::<Vec<&i32>>();

Version

rustc 1.79.0-nightly (aa1c45908 2024-04-06)
binary: rustc
commit-hash: aa1c45908df252a5b0c14e1bcb38c6c55ae02efe
commit-date: 2024-04-06
host: x86_64-unknown-linux-gnu
release: 1.79.0-nightly
LLVM version: 18.1.2

Additional Labels

No response

[matthiaskrgr]

pub fn main() {
    let x = [1, 2, 4, 5, 3, 4, 5, 3, 2, 8, 6, 3];

    // finding
    let z = x
        .iter()
        .map(|n| match n {
            0 | 2 | 5 => Some(n),
            _ => None,
        })
        .flatten()
        .collect::<Vec<&i32>>();

    // suggest:
    let y = x
        .iter()
        .filter(|n| matches!(n, 0 | 2 | 5,))
        .collect::<Vec<&i32>>();

    dbg!(&z);
    dbg!(&y);
    assert_eq!(z,y);
}

[Alexendoo]

The suggestion would trigger unnecessary_filter_map to go to a plain .filter