Is this more of a long term goal, or is it already on it’s way?
Actors are the only way of multi threading there I’m sure what my code is actually doing (it fixes what multithreading breaks in my eyes). And they are nice to use in Kotlin with sealed classes, when, and coroutines. All this things are part of a whole what makes Kotlin interesting enough to use it instead of Java, but native is the missing part of this whole.
Hey there,
there is an issue on kotlinx.coroutine github for multi-threading in Native, you should check it out if you want more info.
TL;DR: K/N memory model is too restrictive to implement anything decent, there is plan to change that but no release date.
1 Like