Sounds more related to async programming in general than to Kotlin coroutines. Maybe it's just that the Kotlin syntax doesn't show the async nature of a function call at the call site. Hopefully Project Loom (fibers) will avoid this impedance mismatch.
-
-
-
When I read that, I was thinking that it might be more about the use of async/await imperative syntax for doing concurrency. It lulls you into thinking it’s synchronous but really, after yielding, you’re in a different thread, which could screw up some locks’ assumptions.
- Još 1 odgovor
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
Scala, corgis, Rust

For me, the interesting part was where the author points out that the assumptions on JVM locks are lost when using coroutines.
