rust-patterns

Error handling in Rust uses Result and the ? operator for propagation. For robust application boundaries, anyhow captures contextual errors, while thiserror structures custom library errors, ensuring maintainable and safe propagation across modules.

Rust ownership prevents data races by enforcing borrowing rules at compile time. For safe concurrency, use Arc<Mutex<T>> for shared state across threads and channels or async/await to orchestrate concurrent tasks without data races.

To refactor a Rust module with idiomatic ownership patterns, apply borrowing discipline to pass references instead of cloning data. Model states safely using enums with exhaustive pattern matching to ensure all variants are handled explicitly during the refactor.

Use traits and generics for zero-cost abstractions in Rust when designing flexible APIs that require polymorphism without runtime overhead. Traits define shared behavior, while generics allow monomorphization, enabling compile-time type safety and performance optimization.

Rust pattern matching works seamlessly with Option and enums for safe state management. Exhaustive matching forces explicit handling of all possible enum variants and Option states, eliminating null pointer dereferences and undefined behavior at compile time.