Is There a Way to Enforce Consistent Pattern Matching Without Impacting Performance?

[Shvngishrma]

Is there a lint in Clippy, or a potential configuration, that would allow for enforcing more structured and consistent pattern matching while being mindful of performance concerns? Should I expect to incur performance costs from enforcing more specific matching, or can it be done efficiently?

Hi Clippy team,

I’ve been working on a project where I want to enforce more consistent pattern matching across the codebase, especially around match statements. My goal is to avoid inefficient patterns like match x { Some(_) => ... } and enforce more specific matches such as match x { Some(value) => ... }, where the value is directly captured.

However, I’m also concerned about performance. I’ve seen performance issues arise when using overly specific patterns or destructuring in matches, particularly in hot code paths. Is there a way to enforce best practices for pattern matching (e.g., forcing specific match arms to destructure) without introducing significant performance overhead?

Looking forward to hearing your thoughts and suggestions!

Best regards,
shvngishrma

[Shvngishrma]

idk im kinda noobie here so please guide in detail :)

[Alexendoo]

Can you give a more concrete example? For example https://rust-lang.github.io/rust-clippy/master/index.html#unnecessary_unwrap could be extended to cover something Some(_) => { x.unwrap() } if it doesn't already

For any suboptimal codegen of pattern matching it would be good if you could open an issue on https://github.com/rust-lang/rust