4 ms·
More than just I read your article about C and memory safety today and went clicking around in the archive. Good work. When I read the Go statement considered
by MarkMarine 4y ago
More than just I read your article about C and memory safety today and went clicking around in the archive. Good work.
When I read the Go statement considered harmful post, I felt the same thing. This just makes sense, everything should be like this. A number of these ideas have been designed into Kotlin’s concurrency library, what are your thoughts about it?
- gavinhoward 4y agoThank you! I haven't seen Kotlin's library, so I can't comment. Do you have a link? I wasn't able to pull up anything good with a search.
- garrybelka 4y agohttps://elizarov.medium.com/structured-concurrency-722d765aa952 https://elizarov.medium.com/structured-concurrency-722d765aa... https://elizarov.medium.com/coroutine-context-and-scope-c8b255d59055 https://elizarov.medium.com/coroutine-context-and-scope-c8b2... https://kotlinlang.org/api/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines/launch.html https://kotlinlang.org/api/kotlinx.coroutines/kotlinx-corout...
- gavinhoward 4y agoThank you! To answer the GGP, this looks like true structured concurrency to me. Chalk one up for Kotlin!