> even seemingly being aware of Notes on structured concurrency, or: Go statement considered harmful [1] > The popular concurrency primitives – go statements,

> even seemingly being aware of Notes on structured concurrency, or: Go statement considered harmful [1] > The popular concurrency primitives – go statements, thread spawning functions, callbacks, futures, promises, ... they're all variants on goto, in theory and in practice. [...] Therefore, like goto, they have no place in a modern high-level language. That's a really long and abrasive article ("Everyone else's stuff is GOTO, but mine isn't") to read just to get to "Wait for your return values before moving on". No mention of any kind of synchronisation primitives, liveness guarantees, determinism, channels, transactions...