rust-best-practices

Idiomatic Rust code reviews apply ownership, borrowing, and lifetime guidelines to improve code quality. You provide a Rust snippet and a review plan to enforce Copy trait usage and borrowing vs cloning decisions based on Apollo GraphQL's best practices handbook.

Error handling in Rust uses Result types to manage failures explicitly. Implementing idiomatic patterns involves applying linting guidance with clippy and following documentation practices to ensure robust API design and proper error propagation.

Yes, these Rust best practices support performance tuning and API design. They enforce front-matter driven metadata and compatibility with Rust 1.70+ and Cargo, aligning refactoring and optimization decisions with real-world scenarios.

You need Copy trait and lifetime considerations in Rust refactoring when deciding between borrowing vs cloning or optimizing ownership patterns. Applying these idiomatic patterns during refactors prevents common memory management pitfalls and improves code quality.

Yes, this Rust best practices skill works with Cargo and clippy linting workflows. It enforces compatibility with Rust 1.70+ and Cargo, providing linting guidance and testing documentation practices aligned with the Apollo GraphQL handbook.