rust-reviewer

Reviewing Rust code for ownership and lifetime safety involves checking borrowing rules, verifying unsafe invariants, and identifying data corruption risks before merging changes. This process targets fragile unwraps and hidden panics to ensure correctness.

Checking async Rust code requires evaluating task lifetimes, cancellation behavior, backpressure, blocking calls, and Send assumptions in concurrent environments. This analysis identifies async hazards that could compromise production reliability.

Yes, reviewing unsafe Rust code in systems code involves verifying unsafe invariants, checking dependency features, and validating MSRV assumptions. This ensures that unsafe blocks maintain their safety contracts and do not introduce memory vulnerabilities.

Catching hidden allocations and feature-flag issues in a Cargo workspace requires flagging unnecessary clones and verifying dependency feature combinations. This maintainability guidance prevents reproducibility problems and performance regressions in Rust libraries.

Yes, Rust code review covers MSRV assumptions and evaluates targeted test coverage for CLIs and services. It identifies missing tests and fragile unwraps, ensuring production reliability and correctness before changes reach users.