code-quality

Enforce Rust code quality during reviews by applying rules for correctness, exhaustive matching, and clear error handling. This standardizes safe coding practices, reduces bugs, and prevents maintainability issues caused by over-engineering or premature abstractions.

The best Rust patterns for maintainable code include using enums over strings, exhaustive matching, and minimal allocations. Favoring simple changes over premature abstractions ensures predictable behavior and reduces maintenance burden.

Yes, you can apply these code quality rules in CI checks for a Rust project. They specify correct Rust patterns, safe coding practices, and error handling guidelines to ensure predictable, maintainable code automatically during integration.

Yes, this Rust correctness approach crashes on invalid state to preserve data integrity. It forbids hacks, requires asserting invariants, and enforces strict rules to ensure data remains valid and predictable throughout execution.

Avoid over-engineering in Rust code to reduce maintenance burden and churn. Favoring simple, maintainable changes over premature abstractions ensures the codebase remains predictable, readable, and less prone to complex bugs during future updates.

Handle errors correctly in Rust by applying clear error handling rules that ensure predictable, maintainable code. Standardizing these practices during code reviews and CI checks prevents hacks and preserves data integrity.