rust-best-practices

Rust code review for borrowing versus cloning requires comparing functions against specific handbook sections to recommend safer ownership and prevent non-idiomatic cloning decisions before production.

Clippy lint compliance is enforced by running cargo clippy with strict settings to catch high-impact warnings like redundant_clone, needless_collect, and large_enum_variant during code review.

Result-based error handling in Rust is reviewed by checking error propagation logic against handbook chapters, ensuring the code uses idiomatic Result patterns rather than panicking or ignoring errors.

Yes, Rust generics and type state patterns are reviewed by applying reference-driven guidance drawn from Apollo's handbook to ensure type safety and idiomatic implementation.

Yes, checking clippy compliance and performance tuning requires Rust 1.70 or higher, Cargo, and precise references to the Apollo handbook chapters before giving feedback.

Pointer modeling and performance profiling are reviewed when evaluating Rust functions, comparing benchmarking approaches and pointer usage against handbook guidelines to prevent performance bottlenecks.