Kotlin Native Concurrency Explained
summary
Explains the actual Kotlin/Native rules: mutable state is visible to one thread only, immutable can be shared; objects must be frozen or passed through workers, or you get InvalidMutabilityException. Shows tools and libs used: Worker API, freeze, ensureNeverFrozen, Atomics (with leaks and perf caveats), and stately (being reworked). Reports that a November 2019 draft PR adds multi‑threaded coroutines, that Droidcon app uses it in production, and that most teams prefer freezing or state‑containers over detached graphs.
AI-written summary · about
chapters (6)
related talks
39mKotlin Native Concurrency Explained
44mKotlin/Native Concurrency for Mobile Multiplatform
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
28mConcurrency for Imposters
26mKotlin/Native for Multiplatform Development