rust-dev-guidelines

The best way to handle errors in async Rust is using the `Result` and `Option` types with the `?` operator for robust, simplified error propagation across asynchronous boundaries without unwinding the stack.

To share state across concurrent Tokio tasks, wrap your data in `Arc` and `Mutex` or `RwLock`. This allows multiple asynchronous tasks to safely access and modify shared memory without data races.

Tokio is heavily utilized in idiomatic Rust for async programming because it provides the runtime necessary for spawning tasks and executing concurrent operations efficiently, as outlined by async best practices.

To avoid async Rust anti-patterns during refactoring, adhere to clippy best practices, ensure proper ownership and borrowing, and use `serde` serialization guidelines to maintain idiomatic code structure.

Use traits and generics in asynchronous Rust applications when you need to define shared behavior across different types or require flexible, reusable components that integrate seamlessly with Tokio's async execution model.