Managing Combine, your existing code, and async/await
summary
Shows how to keep legacy callbacks while adding Combine and async/await: wraps URLSession.dataTaskPublisher and returns AnyPublisher via a Future bridge to avoid duplicating networking code; turns change callbacks into observables with the Published property wrapper; converts callbacks to async functions with unsafe continuation for one-shot calls; warns that tasks implicitly capture self and must be cancelled (use cancelables or weak self), and recommends Combine for state streams and async/await for single start–end tasks.
AI-written summary · about
chapters (24)
- 0:00Introduction and setup
- 1:04Talk overview and context
- 3:52Legacy code patterns in apps
- 6:23Closures and completion handlers
- 8:09Change handlers and state observation
- 10:34Migration strategies for new tech
- 11:58Combine speed run introduction
- 13:42Publishers and subscriptions
- 15:50Combine vs completion/change handlers
- 16:31Networking with Combine
- 17:54Bridging callback code to Combine
- 19:59Future for one-shot actions
- 21:02Replacing change handlers with Combine
- 24:34Location provider with Combine
- 28:43Async/await introduction
- 29:49Networking with async/await
- 30:34Bridging callbacks to async/await
- 31:39Calling async/await functions
- 33:21Async/await for state observation
- 34:03Async streams and sequences
- 36:30Task lifecycle management
- 39:20Combining Combine and async/await
- 41:27Future of Combine vs async/await
- 42:31Q&A session
