Rust Best Practices

Rust error handling should use Result-based propagation instead of unwrap or expect to prevent panics. Use thiserror for libraries and anyhow for binaries to ensure production-safe error management.

Rust ownership guidance prefers references over cloning, using efficient parameter types like &str or &[T]. Choose Cow when ownership is ambiguous to balance performance and safety.

Run cargo clippy with --release benchmarking to catch performance pitfalls. Target specific lints like redundant_clone and needless_collect to identify and remove inefficient ownership patterns.

Use thiserror for libraries to define custom error types and anyhow for binaries to handle dynamic errors. This distinction ensures appropriate Result-based error propagation across your Rust project.

Rust testing practices recommend descriptive test naming, doc tests, and snapshot testing where appropriate. These standards ensure maintainable code and validate module behavior effectively.

Review Rust code by checking ownership handling, error management, clippy lint risks, and performance bottlenecks. Apply quality gates to reduce unsafe patterns and inefficient borrowing before merging.