rust-patterns

Topics in the source

• Rust Development Patterns
• When to Use
• How It Works
• Core Principles
• 1. Ownership and Borrowing
• Use Cow for Flexible Ownership
• Error Handling
• Use Result and ? — Never unwrap() in Production

Idiomatic Rust patterns and best practices for building safe, performant, and maintainable applications. Writing new Rust code Reviewing Rust code Refactoring existing Rust code Designing crate structure and module layout This skill enforces idiomatic Rust conventions across six key areas: ownership and borrowing to prevent data races at compile time, Result/? error propagation with thiserror for libraries and anyhow for applications, enums and exhaustive pattern matching to make illegal states unrepresentable, traits and generics for zero-cost abstraction, safe concurrency via Arc >, channels, and async/await, and minimal pub surfaces organized by domain. Rust's ownership system prevents data races and memory bugs at compile time. | Idiom | Description | |-------|-------------| | Borrow, don't clone | Pass &T instead of cloning unless ownership is needed | | Make illegal states unrepresentable | Use enums to model valid states only | | ? over unwrap() | Propagate errors, never panic in library/production code | | Parse, don't validate | Convert unstructured data to typed structs at the boundary | | Newtype for type safety | Wrap primitives in newtypes to prevent argument swaps | |

This is an excerpt. Refer to the complete source and its current requirements.