rust-patterns

Idiomatic Rust error handling uses Result for explicit propagation, thiserror for custom library error enums, and anyhow for application-level error aggregation. This approach ensures robust, maintainable codebases by enforcing explicit error management at compile time.

Safe concurrency in Rust is best implemented using Arc<Mutex<T>> for shared state and channels for message passing. These patterns prevent data races at compile time through ownership and borrowing rules, ensuring thread safety without runtime overhead.

Ownership and borrowing prevent data races in Rust by enforcing strict compile-time rules over memory access. This Skill guides refactoring snippets to follow these rules, ensuring safe references and mutable borrows that eliminate concurrent modification bugs.

Traits and generics provide zero-cost abstractions in Rust when designing flexible APIs and polymorphic behavior without runtime overhead. Use them to enforce shared functionality across types while maintaining compile-time monomorphization for peak performance.

Yes, this Rust patterns guide covers module organization by domain to improve project structure. It helps teams adopt conventions for ownership, error handling, and concurrency best practices to design robust and maintainable codebases.

Refactoring Rust code to use enums and exhaustive pattern matching models valid states explicitly. This Skill identifies and applies idiomatic patterns to review code, enforcing best practices that prevent invalid states and improve safety.