rust-review

You can review Rust code for async concurrency bugs by performing a multi-lens analysis that evaluates tokio implementations to ensure mutex guards are not held across await points and validates unsafe blocks for soundness.

Auditing unsafe Rust FFI boundaries requires a systematic evaluation of safety invariants and ownership to ensure that unsafe blocks are properly documented and sound against modern Rust edition standards.

Checking Rust project adherence to Edition 2024 standards involves validating ownership, lifetime variance, and trait design through a comprehensive code review process that targets idiomatic errors in complex systems.

Yes, the Rust code review process works with tokio async implementations by specifically evaluating async patterns to catch concurrency pitfalls and ensure production-grade code quality in high-performance services.

You need a deep-dive safety audit for a Rust project when performing pre-production checks on high-performance async services to catch subtle memory safety issues, concurrency bugs, and idiomatic errors before they reach production.