Understanding Rust futures by going way too deep

Re:Understanding Rust futures by going way too deep by ohazi on Monday July 26, 2021 @04:20AM (#27957003)

> I am surprised Rust doesn't lean into the type system more for declaring async, as I really like that way of framing it. Admittedly, I'm probably not writing ```impl Future<Output = Result<(), Report>> + 'a``` all that much in practice.

Futures was stabilized before the async syntax, so this used to be the only way you could do it. But those were definitely the bad old days.

A handful of (brave) developers and library writers wrote async code like this back then when they really needed to, but the vast majority waited for async syntax to stabilize. Those state machines get ugly real fast.

[ Parent | on HN ]

Re:Understanding Rust futures by going way too deep by majewsky on Tuesday July 27, 2021 @05:49AM (#27970535)

> Futures was stabilized before the async syntax, so this used to be the only way you could do it.

While that's technically true (std::future was in 1.36 and async/await syntax was in 1.39), that's a very short timespan of only a few months. You are probably referring to the multiple years where futures only existed as addon libraries where their design was iterated on before the final design of std::future was settled on.

[ Parent | on HN ]