Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.



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.


> 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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: