News for hackers. Stuff that matters.

A comment on State of Loom. Parent comment

Re:State of Loom by balfirevic on Saturday May 16, 2020 @11:11AM (#23204011)
> Can you maybe elaborate why this model is better than async/await?

Others have given actual explanations, but I'll chime in with a bit of a tongue-in-cheek one: it's better than async/await because it doesn't have async/await (yet has all the benefits provided by them).

[ Parent | on HN ]
Re:State of Loom by chrisweekly on Saturday May 16, 2020 @07:58PM (#23208223)
I wish I understood this better. If you're writing code in the same style whether it's async or not, how can you manage return values and reason about flow?
[ Parent | on HN ]
Re:State of Loom by balfirevic on Saturday May 16, 2020 @08:18PM (#23208306)
The flow is sequential, as laid out in the code, the same as for any old-fashioned code. It has the same semantics as the non-async code. The only difference is that OS thread can be released to do some other work while you wait for IO operation to finish.
[ Parent | on HN ]