News for hackers. Stuff that matters.
Re:Even in Go, concurrency is still not easy by mathw on Thursday September 03, 2020 @03:23AM (#24361583)
async/await isn't really concurrency. It's syntactic sugar over callback hell, which can be used to write concurrent software in the "spawn something, wait for it to finish later" model. It has absolutely nothing to help you passing data between ongoing threads, accidental unlocked access to shared data etc. etc.
Re:Even in Go, concurrency is still not easy by unscaled on Thursday September 03, 2020 @05:16AM (#24362213)
This used to be my assumption long ago, but this is incorrect for almost every implementation async await.

The compiler does not syntactically converts your awaits to callbacks - it converts everything into state machines.

Re:Even in Go, concurrency is still not easy by thelazydogsback on Thursday September 03, 2020 @12:58PM (#24366060)
C# converts to state-machines, F# converts to nested callbacks. (Although this may change, or be optional.)
Re:Even in Go, concurrency is still not easy by unscaled on Friday September 04, 2020 @11:29PM (#24381209)
Interesting. The only other instance I remember of (sort-of) awaits being converted into callbacks are LiveScript "backcalls":

https://livescript.net/#functions-backcalls