rust-engineer

To design ownership-safe Rust system components, you analyze ownership flows, establish appropriate lifetime relationships, and apply borrowing patterns alongside idiomatic async/await designs using tokio for high concurrency and predictable memory safety.

The best way to structure async services in Rust using tokio involves applying idiomatic async/await designs, managing task spawning and cancellation, and utilizing channel-based communication to ensure safe ownership and high concurrency.

Handling errors in high-performance Rust libraries requires explicit Result and Option patterns, custom error types, and documented unsafe blocks, ensuring zero-cost abstractions while preventing undefined behavior and runtime errors.

To build extensible trait-based APIs in Rust, you define trait hierarchies, utilize generics and associated types, and apply conversion patterns, ensuring the architecture supports zero-cost abstractions for performance-critical libraries.

Testing Rust systems programming components involves writing unit, integration, and property tests, running benchmarks with criterion, and using MIRI to verify unsafe blocks, ensuring clippy and rustfmt conformance.

You need explicit lifetimes and borrowing patterns in Rust when designing performance-critical libraries and FFI bindings where predictable ownership is required to avoid runtime errors and maintain zero-cost abstractions without garbage collection.