rust-best-practices

Use thiserror for typed errors in library crates to provide clear public APIs, and use anyhow at binary crate boundaries for flexible application-level error handling. This separation maintains clean workspace conventions and prevents hidden failure modes.

Enforce Rust best practices by applying strict clippy lint discipline, requiring explicit guardrails against unsafe code, and replacing unwrap or expect calls with proper Result and Option handling to eliminate hidden failure modes.

Structure Rust modules by following workspace rules for newtypes, trait naming, re-exports, and file boundaries. Review public API surface area changes against these conventions before adding new public functions or error types.

Yes, clippy allow decisions require workspace-wide standards to maintain strict formatting and lint discipline. Check unit tests, integration tests, and lint warnings against workspace policy before approving any clippy allow additions.

Review Rust code changes by checking error types, Result and Option choices, module naming, and testing patterns against workspace policy. Focus on typed errors with thiserror in libraries and anyhow boundaries in binaries.

Rust libraries need typed errors to define stable public APIs that callers can match on reliably. Using anyhow in a library public surface hides failure modes and prevents downstream code from handling specific error variants explicitly.