How To Approach Approachable Concurrency
summary
Swift 6.2 ships concrete changes from SE0461 that aim to make data‑race safety more approachable: a new default-setting bundle called approachable concurrency, an automated migration tool for changing nonisolated async behavior, and the new sendable metatype plus a nonisolated non‑sending variant to avoid implicit actor hops. Runtime behavior can differ by OS (a cast can behave differently on older runtimes), protocol conformance can become isolation‑dependent, and library authors must update APIs; the migration tool successfully makes most fixes automatically.
AI-written summary · about
chapters (14)
- 0:00Why concurrency matters
- 1:10Swift Concurrency overview
- 3:55Swift 6.2 vision document
- 5:18Default isolation changes
- 7:26Protocol conformance issues
- 9:55Runtime vs compile-time behavior
- 11:20Nonisolated async functions
- 13:09Nonisolated non-sending
- 14:35SE0461 changes
- 15:38Compiler settings guidance
- 16:42Complete checking trade-offs
- 17:25Swift 6 language mode
- 18:07Main actor default choice
- 18:50Take your time with concurrency
related talks
23mSwift Concurrency is new and hard, and you can do it
31mIsolation, actors, sendable… a concurrency deep dive
30mA Practical Guide to Swift Concurrency
45mHow We Adapted the Project to Strict Concurrency Checking — Swift 6
26mSwift Concurrency Under the Hood
31mIs structured concurrency worth the effort?
36mA Deep Dive Into Sendable
41mA Deep Dive Into Sendable for the Apple Developer