Post

I feel like there would be a HUGE amount of ecosystem value for Rust and async/await, if there was funding and the right dev(s) available to focus on improving: * Memory usage + copies of futures/async fns: particularly wrt overlapping data across yield * Improving codegen size/perf * opt-footguns

None of these are *deal breakers*: and should not be a reason to NOT use async/await, IMO. But on embedded we feel the pain of increased code size + ram usage much more acutely, and sometimes it requires being careful to avoid pathological cases. That doesn't feel good.

It's probably a bit more lost in the noise on desktop on a macro scale, but I'd bet the improvement would be noticable, especially for large/complex server apps. bsky.app/profile/shar... shows it extends to causing issues with llvm opt passes too!

sharnoff@sharnoff.io

Spent the last ~month trying to figure out why compiling my website took so long. Decided to turn it into a blog post :) sharnoff.io/blog/why-rus...

I'm probably not the person to actually do this: there are much more compentent rustc devs than me, but the impression that I've always gotten is that there are known areas where improvement could be made, but finding people to chase them down and get fixed AND reviewed/merged hasn't been possible.

0 reposts6 likes

No replies yet.