Swift 6, Async/Await, SwiftUI went into a Bar...
summary
Migrating a real app to Swift 6 and SwiftUI takes about a year and reveals concrete pitfalls: code often belongs on the main thread, not automatically moved to background; an actor-based image cache issues causes two loads instead of one because an await suspends and lets another caller run; fix is to track ongoing tasks and await them. The talk demos using async/await, actors, async stream with continuations for CoreLocation and explains the sendable box tradeoffs, plus using Instruments to decide what to offload.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 5:34Three core migration topics
- 6:42Revisiting the main thread
- 11:45Understanding await keywords
- 14:36Classes versus actors
- 19:23Reentrancy and cache bugs
- 25:04Async sequences for services
- 32:30Conclusion and Q&A
related talks
35mThe Multi-Threaded Asynchronous Parallel World of Swift
31mYour Brain 🧠 on Swift Concurrency
35mSwiftUI, Async/Await, AsyncAlgorithms: How does it all fit?
24mSwiftUI Performance Tips
39mSwift and You
42mAsync Await and More in Swift
23mSwift Concurrency is new and hard, and you can do it
02h 42mSwift Structured Concurrency