rust-patterns

Error propagation in Rust libraries should use thiserror for structured custom errors, while applications should use anyhow for flexible context-based error handling to maintain clear abstractions and maintainability.

Share data safely across threads in Rust by using Arc<Mutex<T>> to provide atomic reference counting and mutual exclusion, or use channels to pass messages and prevent data races at compile time.

Use exhaustive enums and pattern matching to model valid states in Rust, ensuring the compiler forces you to handle all possible variations, which prevents invalid state bugs and improves code safety.

Use unsafe code in Rust only when you need to interface with hardware or optimize beyond safe Rust capabilities, following strict guidelines to ensure the encapsulated operations do not violate ownership or borrowing rules.

Use traits and generics to create zero-cost abstractions in Rust, allowing flexible, polymorphic APIs without runtime overhead by ensuring type safety and monomorphization are handled at compile time.

Common ownership and borrowing issues in Rust cause data races and compile-time errors, which you fix by applying idiomatic patterns like proper lifetime annotations and structuring data to prevent simultaneous mutable access.