News for hackers. Stuff that matters.
Re:Why asynchronous Rust doesn't work by ha_jo_331 on Wednesday March 10, 2021 @06:51AM (#26410289)
Of course a fiber/green threads based solution would be easier to use, but Rust is supposed to provide zero cost abstractions for concurrency: Maximum performance and efficiency (and safety) coming first, usability second. THat is perfectly fine.

Whereas others (Go for example) sacrifice some efficiency and performance to ergonomics.

Re:Why asynchronous Rust doesn't work by jedisct1 on Wednesday March 10, 2021 @07:28AM (#26410529)
Is it still zero cost if the price to pay is a steep increase of code complexity?

The current model also still requires a lot of boxing and cloning, so it is far from being “zero cost” as advertised.

Re:Why asynchronous Rust doesn't work by steveklabnik on Wednesday March 10, 2021 @12:19PM (#26413624)
> Is it still zero cost if the price to pay is a steep increase of code complexity?

Yes, because the "cost" in "zero-cost" only refers to runtime cost.