m07-concurrency

To resolve Rust Send and Sync trait compile errors, map the specific error like E0277 to design questions about your async boundaries. This Skill analyzes your concurrency failures and recommends appropriate thread-safety strategies, selecting proper synchronization primitives or restructuring async tasks.

Choosing between tokio async and std::thread requires evaluating your domain constraints and workload type. This Skill provides decision flowcharts that trace project context to recommend the correct concurrency model, synchronization primitives, and message passing patterns for safe implementation.

Your Rust async code deadlocks with Mutex because holding a lock across an await point blocks the executor thread. This Skill identifies deadlocks and suggests safe concurrency patterns using alternatives like channels, RwLock, or atomics to prevent blocking async runtime tasks.

To select the right Rust synchronization primitive, evaluate whether your workload needs exclusive write access or concurrent reads. This Skill lists safe patterns for Arc, Mutex, RwLock, channels, and atomics, matching them to your specific domain constraints and threading model.

You can use rayon and tokio together by offloading CPU-bound parallel tasks to rayon while tokio handles async I/O. This Skill provides guidance on selecting threads, async runtimes, and message passing to ensure safe integration without modifying your existing code.