senior-rust-code-reviewer

Rust code review for memory safety and concurrency issues requires analyzing unsafe blocks, FFI boundaries, and concurrency primitives to validate safety justifications and prevent data races or undefined behavior.

The best way to check a Rust pull request for performance regressions is to analyze code changes for potential performance bottlenecks and ensure that new logic does not introduce inefficiencies in performance-critical sections.

To validate safety justifications for unsafe blocks in Rust, review the code to ensure the invariants preventing undefined behavior are thoroughly documented and that FFI calls maintain memory safety boundaries.

Yes, you can use an automated review to check Rust API design and stability by analyzing public APIs to ensure they are stable, well-documented, and clearly structured for consumers.

Common race conditions and deadlocks to look for in Rust concurrency involve improper synchronization of concurrency primitives, which can lead to data races and undefined behavior if safety justifications are invalid.