<@U1TCY49GT> You can look at this way, but all abs...

# coroutines

[elizarov]

@dstarcev You can look at this way, but all abstractions in software engineering are inherently leaky. When I use a property I assume that it is non-blocking and works in O(1). That’s the convention, but we don’t have a way to enforce it. When I use a method that returns some kind of future I assume that the method itself is non-blocking, but I have no way to be 100% sure. That’s just a sane engineering discipline. The same with suspend. Btw, if any of the above is blocking because it logs, the it is usually not a big deal. It is a different kind of blocking. It will not freeze my app if WiFi goes dead.