News for hackers. Stuff that matters.
Re:Rust async-await status report 2 by steveklabnik on Wednesday July 10, 2019 @04:57PM (#20406474)
There are people playing with them, but I don’t know how mature they are. Actix is one example.
Re:Rust async-await status report 2 by Footpost on Thursday July 11, 2019 @04:14AM (#20409941)
Would you be able to venture a guess why they are not more popular? I agree that basing Rust's concurrency on an Erlang-like model would not have been a good idea, for reasons mentioned in this thread. Nevertheless the sheer convenience of Erlang-style concurrency would nevertheless be useful in quite a few scenarios where Rust is used.
Re:Rust async-await status report 2 by Footpost on Thursday July 11, 2019 @07:19AM (#20410680)
I'm asking because I'm considering developing an Erlang-like approach to message-passing concurrency for Rust.
Re:Rust async-await status report 2 by steveklabnik on Thursday July 11, 2019 @11:27AM (#20412277)
I dunno, it just seems philosophically divergent. Rust isn't afraid of sharing, that's kinda the whole point.

actix was a big one, but actix-web ended up moving off of it, so I'm not sure what the state of it is.