News for hackers. Stuff that matters.
Re:How Rust Is Tilde’s Competitive Advantage [pdf] by eropple on Tuesday February 06, 2018 @03:12PM (#16319169)
C# was, as far as I'm aware, the first major language to implement async/await atop of Task<T> (akin to Java's Future<T>). The CLR uses native threads.

Go channels are also orthogonal to async/await. Message passing is not a substitute for futures/tasks, though it can be used to achieve similar goals. I would be extremely cautious about claiming that Go channels would be "more performant" than an otherwise-equivalent futures implementation, too.

Re:How Rust Is Tilde’s Competitive Advantage [pdf] by wahern on Tuesday February 06, 2018 @06:02PM (#16320769)
Goroutines are not the same thing as Go channels.
Re:How Rust Is Tilde’s Competitive Advantage [pdf] by eropple on Tuesday February 06, 2018 @06:27PM (#16320959)
Sorry, yes. Fibers (Go didn't invent them) also aren't directly equivalent because they don't allow explicit yields and composition.
Re:How Rust Is Tilde’s Competitive Advantage [pdf] by wahern on Tuesday February 06, 2018 @08:12PM (#16321512)
Fibers don't, but goroutines + channels + closures do. They permit composition using the same call/return syntax and semantics as normal function calls.

Futures and promises don't. Async/await is closer, but only by creating a second class of function incompatible with normal functions.