m07-concurrency

Rust concurrency design: workload classification, sharing models, and Send/Sync requirements. Layer 1: Language Mechanics Is this CPU-bound or I/O-bound, and what's the sharing model? Before choosing concurrency primitives: Before adding concurrency: What's the workload? What's the sharing model? What are the Send/Sync requirements? CRITICAL : Don't just fix the error. Trace UP to find domain constraints. From design to implementation: - Guides decision-making between threads (CPU-bound), async (I/O-bound), and hybrid approaches before implementing - Covers Send/Sync marker traits, thread-safety patterns (Arc, Mutex, RwLock, channels), and atomic operations with quick reference tables - Includes mandatory "trace up" to domain skills (web, fintech, cloud-native, CLI) to align concurrency design with architectural constraints - Highlights anti-patterns like holding MutexGuard across await, ignoring deadlock risk, and overusing Arc for message passing - What's the workload type?