rust-standards

Enforce no unwrap or expect in Rust core crates by applying coding standards that ban these methods in library code and permit them only in tests, ensuring safety and preventing runtime panics during execution.

Handle errors in Rust without panics by using thiserror for crate-local error types and mapping external errors at boundaries, explicitly eliminating panic macros from library code to ensure deterministic safety.

Ensure deterministic iteration in Rust codebases by applying standards that require explicit ordering for any iteration affecting semantics, guaranteeing consistent processing order and deterministic behavior across operations.

Yes, this Rust code quality standard requires strict rustfmt and clippy compliance across the codebase, enforcing idiomatic formatting and static analysis checks during code generation, refactors, and reviews.

Rust library code fails static analysis checks when it contains unwrap, expect, or panic macros, lacks thiserror error types, or violates clippy and rustfmt compliance rules during linting.