Rust Code Reviewer

Review Rust code targeting the specific failure modes that AI-generated and human-written Rust most commonly gets wrong. Not a generic code review — Rust-specific.

Review Checklist (ordered by severity)

1. Unsafe Code Audit (critical)

First: is unsafe even necessary?

• FFI calls → yes, required
• Raw pointer deref → yes, but can it be restructured to avoid raw pointers?
• Mutable statics → yes, but consider OnceCell, LazyLock, or atomics instead
• Implementing Send/Sync → yes, but verify the type genuinely satisfies the contract
• Bypassing borrow checker → no. The design is wrong. Redesign it.
• Performance → maybe. Must have measured proof.