News for hackers. Stuff that matters.

A comment on Async and Await in Rust: a full proposal. Parent comment

Re:Async and Await in Rust: a full proposal by Manishearth on Monday July 16, 2018 @11:36AM (#17542111)
"impossible" is a highly contextual term here. Adding this to Rust isn't "impossible", of course it isn't. We can "just" slowly turn Rust into Haskell using the edition mechanism. Done.

When folks say something is "impossible" in such a context, they mean "given the constraints", which include goals the lang team has for the language. An effects system is pretty heavyweight and may violate these goals.

[ Parent | on HN ]
Re:Async and Await in Rust: a full proposal by withoutboats on Wednesday July 18, 2018 @09:24AM (#17558138)
I think that there is not a definition of the Monad trait - not just undesirable, not possible - that can abstract over all Futures and Iterators as implemented in Rust. You would have to use some kind of trait object & lose the incredible inlining benefits that Rust gets from how these interfaces are designed today.

This is separate from effect systems, which I never said was not possible. rpjohnst's parallel response sums up the key differences between monads and an effect system.

[ Parent | on HN ]