rust-best-practices

Idiomatic Rust code for ownership and borrowing minimizes unnecessary clones by applying strict guidelines, ensuring memory safety without runtime overhead. It provides specific rules for choosing borrowing over cloning to avoid common performance pitfalls.

The best way to handle errors in Rust is using Result, thiserror, and proper error propagation instead of panicking. This strategy improves code reliability by ensuring errors are explicitly handled and bubbled up to the caller cleanly.

Configuring clippy lints for Rust performance involves applying linting recommendations that identify unnecessary clones and promote zero-cost abstractions. This process targets performance trade-offs early, reducing runtime overhead and review time.

Standard testing and documentation practices for Rust involve creating robust tests and clear public APIs. Aligned with Apollo's handbook, these practices ensure comprehensive test coverage and well-documented public interfaces for maintainable code.

You should refactor Rust code to avoid unnecessary clones when reviewing tasks for performance bottlenecks. Applying borrowing and ownership guidelines during refactoring eliminates abstraction violations and improves overall execution speed.