code-quality

To enforce Rust code quality during reviews, check that functions assert invariants, use explicit Result<_, _> error handling, avoid unwraps, and match exhaustively. This prevents silent failures and ensures correctness.

Best practices for Rust error handling involve preferring explicit Result<_, _> types over unwraps to avoid silent failures. Asserting invariants and using exhaustive matching further prevents data corruption and bugs.

You need to assert invariants in Rust functions whenever specific conditions must hold true to prevent bugs and data corruption. Asserting invariants catches edge cases early, ensuring code correctness and robustness.

To minimize allocations and avoid structural bloat in Rust, follow production-grade patterns like type-safe enums and minimal allocations. Clear comments and robust patterns help maintain readability and prevent over-engineering.

Yes, you can use these code review guidelines for Rust projects of any size. The rules scale from small functions to large refactoring tasks, guiding maintenance to ensure correctness, readability, and safety.

Rust code may fail to catch edge cases during refactoring if it lacks invariant checks and exhaustive matching. Applying correctness-first guidelines and explicit error handling prevents these silent failures.