rust-patterns

To avoid unnecessary cloning in Rust ownership and borrowing, apply standardized patterns that leverage the compiler's strict rules for compile-time memory safety. These idiomatic patterns eliminate workarounds by ensuring correct reference lifetimes and data access without duplication.

The best way to handle errors in Rust without causing panics is using standardized error handling patterns. By utilizing Result, the ? operator, and crates like thiserror and anyhow, you create robust error flows and avoid production crashes from unwrap() calls.

To implement safe concurrency with shared state in Rust, use standardized patterns for thread-safe execution. Guidance covers implementing Arc<Mutex<T>> and channels to achieve safe concurrent execution while satisfying compile-time data race prevention requirements.

Yes, you can use this Skill to refactor an existing Rust codebase for code review. It applies to Rust development workflows including new code authoring, refactoring, and code review, eliminating non-idiomatic, bug-prone code through actionable best practices.

Your Rust crate structure may lead to suboptimal performance and safety bugs due to non-idiomatic module design. Applying domain-based crate structure patterns ensures a minimal public API surface exposure and scalable, maintainable codebases.