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

Especially in embedded, I presume.

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

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.

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.

What’s the reasoning for the nested future depth? That it causes monorphization woes? Do all the nested futures get inlined?

github.com/rust-lang/ru... is an easy go-to, but in general yeah there's a lot of very-not-optimized codegen going on wrt generators/futures.