rust-patterns

To handle errors in Rust safely, use the `Result` type with the `?` operator instead of `unwrap()`. For production-grade error handling, define library errors with `thiserror` and add application-level context using `anyhow`.

The best way to satisfy the borrow checker without excessive cloning is using references and preferring `Cow` for flexible ownership. This approach enforces idiomatic ownership patterns to maintain performance while keeping code safe.

Structure Rust crates by organizing modules according to domain boundaries. To maintain clean API design, minimize `pub` surfaces to keep public boundaries tight, which makes the module layout scalable and easier to maintain.

Use enums for state modeling in Rust when you need exhaustive matching to ensure all possible states are handled safely. This robust modeling practice prevents unhandled edge cases during compilation and improves code reliability.

Yes, this Rust concurrency guidance covers Tokio async patterns alongside safe concurrency primitives like `Arc<Mutex<T>>` and channels. It helps implement safe concurrency using threads and asynchronous runtime patterns effectively.

Yes, you can use this to refactor existing Rust codebases for clarity and safety. It reviews code to enforce idiomatic ownership, error handling, enum modeling, concurrency approach, and minimal public API surface.