4 ms·
Just the other day they were full kum ba yah over a holiday-time-released feature that's likely going to greatly increase the likelihood of building race condit
by meltyness 3y ago
Just the other day they were full kum ba yah over a holiday-time-released feature that's likely going to greatly increase the likelihood of building race conditions and deadlocks.
https://news.ycombinator.com/item?id=38721039 https://news.ycombinator.com/item?id=38721039
- jvanderbot 3y agoI know it's the curmudgeon NIMBY in me, and I love Rust and use it daily, but it's starting to feel like the worst of the JS crowd scribbled in grandpa's ANSI C books just to make him mad. I am super happy with most features, but demand is demand and people demand runtimes. As a chimera it perfectly represents the modern world.
- zanellato19 3y agoThis is such a bizarre take on the stabilization of async that I can't even tell if you are being serious or just hate Rust.
- dartos 3y agoHow do you figure? Is it just because it makes async possible?
- meltyness 3y agohttps://rust-lang.github.io/async-book/03_async_await/01_chapter.html#awaiting-on-a-multithreaded-executor https://rust-lang.github.io/async-book/03_async_await/01_cha... Is this all information that should be communicated to a programmer, or is all this info something that should be automatically assessed by a compiler with clear responses automatically to all possible situations specified, black and white, in the code? If so, if it is the responsibility of the compiler, why release a version of the language, stabilize a spec, where that's not the case?
- jcgrillo 3y agoTo be clear you're talking about async fn and impl trait in return position in traits? If so, how does that impact the likelihood one way or the other of race conditions or deadlocks?