Hey guys, Thinking about the most recent talking-k...
# coroutines
g
Hey guys, Thinking about the most recent talking-kotlin podcast where they talk about "a determined junior developer will always be able to write terrible code", I'm wondering if kotlin, specifically coroutines, exacerbates the problem. Consider a
launch { ...
block that calls
Thread.sleep
, or more sophisticated concepts (blocking
queue.take()
etc). This is clearly in error, and they caller likely meant to either
delay
or _needs to learn how to use use of a channel instead of a
BlockingQueue
... can we do better than intelliJ kotlin plugin warnings for such circumstances? I know that AST or byte-code analysis will never be able to get all (or even most) of the ways to call such functions from coroutine blocks, but is it worth some kind of effort?