![]() States were mutable from multiple threads in JVM code, but they didn't need to be. In many cases, simply changing your approach to how you design your code will work fine, and you don't need concurrent mutability. The result of following these rules is that you can't change global states, and you can't change the same shared state from multiple threads. When it comes to working with iOS, Kotlin/Native's state and concurrency model has two simple rules.Ī mutable, non-frozen state is visible to only one thread at a time.Īn immutable, frozen state can be shared between threads. Check out Kotlin/Native memory management to learn about the new memory manager, which has been enabled by default since Kotlin 1.7.20. This page describes the features of the legacy memory manager.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |