I was reading about workers, the new concept introduced in Kotlin native. I’m wondering, the mechanism of data transfer between threads to prevent concurrent access to the same data, is something mandatory? I mean the classical unchecked heap access of multiple thread to memory will still be available or not? Isn’t the transfer or data a major performance hit in some scenarios?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Notlin native and threads | 3 | 1466 | June 19, 2020 | |
| Fearless concurrency in Rust | 11 | 4687 | April 28, 2015 | |
| Native Threading Obersavtions | 3 | 1160 | May 3, 2018 | |
| Kotlin Native and GCD(Grand Central Dispatch) | 1 | 1499 | July 3, 2017 | |
| Does Kotlin/Native have direct memory access as C | 3 | 2757 | July 20, 2017 |