m15-anti-pattern

Rust anti-pattern detection flags flawed ownership designs and fragile error handling by mapping code smells like unwrap-in-production and clone-everywhere to root causes. It then specifies concrete idiomatic refactors such as proper references and safer error strategies.

Common Rust code smells include clone-everywhere, unnecessary Rc usage, unsafe-by-convenience, and giant match arms. These anti-patterns indicate flawed ownership design and fragile error handling that require refactoring toward idiomatic Rust types.

Refactoring deep nesting and long functions involves extracting abstractions and adopting iterator-based iteration. This improves maintainability by replacing complex control flow with idiomatic Rust patterns and proper error propagation using the ? operator.

Yes, this approach reviews Rust code with unsafe blocks by identifying unsafe-by-convenience anti-patterns and mapping them to safer alternatives. It also addresses performance hotspots by recommending ownership-correct designs and idiomatic iteration patterns.

The best way to replace unwrap calls in production Rust code is to adopt safer error handling strategies like the ? operator for proper error propagation. This refactoring resolves fragile error handling anti-patterns by ensuring errors are managed idiomatically.