Kotlin/Native Concurrency for Mobile Multiplatform
summary
Explains concrete rules: mutable state is single‑threaded, shared state must be frozen, and freeze and ensureNeverFrozen are the runtime primitives that cause or prevent invalid mutability exception. Shows tools and libraries that work and fail in practice: workers, stately isolate for thread‑local mutable containers, atomic refs, SQLDelight flows, and the draft of multi‑threaded coroutines. Demonstrates patterns, a plugin that detects freezing mistakes, and tradeoffs — the libraries mostly work but multithreaded coroutines are still experimental.
AI-written summary · about
chapters (8)
- 0:00Intro
- 3:49Kotlin Native Rules
- 7:07Core Concepts
- 14:06Debugging Issues
- 20:32Concurrent Mutability
- 26:58Multiplatform & State
- 29:32Concurrency Libraries
- 37:02Next Steps
related talks
39mKotlin Native Concurrency Explained
39mKotlin Native Concurrency Explained
46mKotlin/Native Concurrency Model
42mKotlin Multiplatform multithreading old and new way
58mKotlin Multiplatform: Memory management old and new way
41mCoroutines for Kotlin Multiplatform in practise
31mKotlin Multiplatform
42mEmbracing the Future in a Multiplatform World: A Kotlin Story
