When Rust hurts
I really resonate with the async complaints in the article. Rust concurrency is <i>not</i> fearless. I fear writing async code every time I have to do it. I have to think so much harder which ultimately means opportunity for errors.<p>Even though Rust does slightly skirt the colored function issue, my code still bifurcates because truly correct async code needs to use async variants of the standard lib for file access. Knowing when something you call blocks, or grabs a lock, etc. is something which the compiler doesn’t help you with but should. And then how the hell are you supposed to use any code sanely when the entire community is using different async runtimes? Why can’t the runtime be part of the core language with hooks into parts that might need to be customized in hyper special cases?<p>It really feels like we lost the steam behind async Rust and we’ve got this partially complete thing that’s neither high level enough to be convenient nor low level enough to be fearlessly correct. Async traits still aren&#x27;t a thing and it’s been <i>years</i>.