Swift Concurrency Under the Hood
summary
Dives into concrete behavior: the compiler runs a task synchronously when no await is present, task groups automatically cancel remaining tasks and propagate the first thrown error, the cooperative pool spawns threads proportional to CPU cores (examples: iPhone SE vs Mac), actors expose an unowned executor for serialized isolation, and distributed actors resolve by ID over a transport so plugins can run in separate processes or on remote GPUs. compiler runs task synchronously automatic cancellation of task groups cooperative pool scales to cores
AI-written summary · about
chapters (4)
related talks
23mSwift Concurrency is new and hard, and you can do it
31mYour Brain 🧠 on Swift Concurrency
20mHow To Approach Approachable Concurrency
45mThreads, Queues, and Things to Come: Present and Future of Concurrency in Swift
02h 42mSwift Structured Concurrency
30mA Practical Guide to Swift Concurrency
42mAsync Await and More in Swift
47mDo We Really Need Swift Modern Concurrency?