rust-core

Fix Rust ownership and borrowing errors by analyzing ownership transfer rules, lifetime elision, and trait design to propose concrete, idiomatic code improvements. This ensures clear intent and minimizes runtime errors across small to large Rust crates.

You need explicit lifetimes in Rust API design when lifetime elision rules cannot automatically infer the correct relationships between references. Analyzing lifetime management ensures robust public APIs and safe borrowing patterns.

The best way to minimize unsafe code blocks in Rust is to enforce strict ownership transfer rules and leverage trait-based abstractions. This approach provides safe interop guidance and reduces the surface area of unsafe operations.

Handle errors idiomatically when designing Rust traits by applying robust error handling patterns within your public API boundaries. This ensures trait design principles maintain safe, predictable execution across your crate.

Yes, this Rust code review guidance works for large crates by systematically addressing ownership, borrowing, and lifetime correctness across varying scales. It enforces trait design and error handling rules applicable to complex module interactions.

Your Rust borrowing pattern fails during code review when it violates ownership transfer rules or lifetime constraints. Analyzing these patterns clarifies intent and enforces safe, idiomatic code boundaries.