rust-review

Review Rust code for ownership and lifetime issues by analyzing source files and manifests to identify unnecessary clones, improper borrowing, and incorrect lifetime annotations. This reduces subtle memory bugs and improves maintainability across library, web service, and systems projects.

Auditing unsafe Rust blocks involves flagging code that lacks safety rationale and verifying FFI boundaries for correctness. This ensures that unsafe usage is properly justified and that foreign function interfaces maintain memory safety guarantees.

Yes, you can check async Rust code in tokio, actix, or axum projects. The review audits concurrency patterns to detect deadlocks, blocking operations in async contexts, and incorrect task spawning to ensure runtime correctness.

Identify panic and unwrap usage in Rust web servers by evaluating error handling patterns across the codebase. The review flags unwrap calls and panic risks, providing practical suggestions for idiomatic error handling improvements.

Yes, a Rust code review checks Send and Sync trait implementations. It verifies incorrect Send and Sync bounds to prevent data races and ensure thread-safe concurrency across async and multi-threaded systems components.