Post

James Munns
@jamesmunns.com

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

James Munns
@jamesmunns.com

Yep, we notice it acutely! bsky.app/profile/jame...

James Munns@jamesmunns.com

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.

Stefan Baumgartner
@deadparrot.dev

Hehe, I thought so. I haven't done much embedded development, but I found situations that would greatly benefit from the ability to asynchronously execute tasks based on certain events. I guess Embassy helps a lot, but it can just be as good as the underlying foundation.

0 reposts0 likes

James Munns
@jamesmunns.com

Yeah, most of these things are *avoidable* in practice: making sure you don't have large owned items in futures, try to keep nested future depth low, etc. It's just annoying you HAVE to work around papercuts.