m07-concurrency

To prevent deadlocks in Rust async concurrency, avoid holding mutexes across await points and ensure futures remain Send. Use structured concurrency patterns with channels to coordinate tasks safely across I/O-bound workloads.

Selecting between threads and async Tokio depends on the workload: use OS threads for CPU-bound parallelism and Tokio async tasks for I/O-bound concurrency. Structured concurrency patterns help manage mixed workloads effectively in Rust services.

You need Send and Sync bounds in Rust async tasks when passing data across threads or spawning tasks on a multi-threaded Tokio executor. These thread-safety guarantees ensure non-Send types do not cause runtime errors in concurrent environments.

Implement structured concurrency in Rust by using channels for task communication and Arc for shared ownership across spawned tasks. This pattern ensures safe parallelism, robust error handling, and clear task lifecycles in complex async applications.

Common Rust async anti-patterns include holding mutexes across await points, which causes deadlocks, and spawning non-Send types into multi-threaded executors. Avoid these by using scoped locks and ensuring task futures satisfy Send bounds.