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.

Code size is an issue for all languages that heavily rely on templates or generics. It's an equally big problem in the world of C++ (although C++ has more common alternatives to help keep it in check).