This breaks hawock when it combines with mutable s...

# random

[elizarov]

This breaks hawock when it combines with mutable state. However, Kotlin already has some tool to help you write code with less mutable state (val) and will be adding more over time. Coroutines actually as solution, because you can isolate mutable state inside coroutines (which are sequntiel, just like actors or agents). They will not prevent you from modifying some mutable state from the outside world, but that is a separate problem to solve, not related to coroutines directly. Coroutines help you achieve this isolation, write the code in this actor/agent-style model (if you will) without making it look cumbersome, without extra callback chains, without extra objects, etc.