Swift Concurrency's Pit of Success
summary
Argues that the real “pit of success” in Swift Concurrency is non-Sendable types and shows why they become useful once Swift 6.2 adds non-isolated non-sending (feature-flagged, rolling into a future language mode). Explains concrete tradeoffs: actor/main-actor checking forces many errors, unchecked sendable hides bugs, starting Tasks inside non-sendable classes is disallowed, and diagnostics can be confusing. Demonstrates that deferring concurrency modeling until it’s needed yields simpler APIs and clearer compiler feedback when concurrency requirements actually arise.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:00Swift concurrency overview
- 4:46Sharp edges in concurrency
- 8:59Modeling behavior with types
- 13:14Non-sendable types benefits
- 15:44Non-isolated non-sending feature
- 17:50Starting with clean slate
- 19:13Conclusion
related talks
48mStructured Concurrency: Writing Safer Concurrent Code with Coroutines...
29mLeveraging structured concurrency in your applications
37mManaging Side Effects with Swift
24mData-Race Safety for the Masses
01h 21mStructured Concurrency
32mStructured Concurrency: The paradigm shift
45mTaming the Chaos - Structured Concurrency
33mChanneling the Inner Complexity