rust-quality

Enforce Rust API design guidelines during code reviews by verifying UpperCamelCase types, snake_case functions, and consistent trait implementations, ensuring shippable, idiomatic Rust code across libraries and binaries.

Handle errors in Rust crates using Result-based patterns with thiserror or anyhow, documenting safety and failure modes. This discipline promotes robust error handling and improves crate reliability and maintainability.

Clippy pedantic lint discipline applies to no_std and embedded Rust projects, enforcing strict lint rules and robust documentation. It ensures conformance to Rust API Guidelines across varied project types including async and GPU-accelerated crates.

Document unsafe blocks with SAFETY notes in Rust code reviews by forbidding unsafe code without thorough safety documentation. Enforce strict safety discipline to ensure all unsafe blocks are properly justified and tested.

Your Rust crate needs prelude exposure and rustdoc coverage to ensure ergonomic API consumption and proper documentation structure. Encouraging proper module layout and rustdoc coverage improves maintainability and developer experience.

Yes, you can apply Rust quality review rules to async and GPU-accelerated crates. The review process enforces API design, error handling, and lint discipline across all crate types, ensuring conformance to Rust API Guidelines.