rust-engineer

Rust's ownership system enforces memory safety at compile time through ownership, borrowing, and lifetimes. Every value has one owner; references borrow temporarily with compiler-verified lifetimes, eliminating data races and use-after-free bugs without runtime overhead or garbage collection.

Use tokio for async runtime and structure services around traits for composability. Tokio handles tasks, I/O, and timers; combine async/await syntax with proper error handling via Result/Option to build high-performance concurrent services.

Traits define shared behavior across types; generics parameterize functions and structs to work with multiple types. Together they enable flexible, type-safe abstractions without runtime polymorphism overhead, supporting composition-based API design.

Explicit error handling via Result and Option forces developers to handle failures at compile time rather than risking panics or silent failures. This makes error paths visible, testable, and guarantees robustness in production systems.

Unsafe code is allowed for FFI bindings, performance-critical sections, and low-level operations where the compiler cannot verify safety. Always document unsafe blocks with invariant comments and minimize their scope to maintain overall system safety.

Use cargo fmt for formatting, clippy for linting, and comprehensive unit and doc tests throughout. These tools enforce consistency and catch common mistakes, ensuring code adheres to Rust idioms and best practices before deployment.