I'm a bit of a broken record, but I will summarize my experience as someone who builds a lot of Rust web services as: 1. My overall experience with async is ve

I'm a bit of a broken record, but I will summarize my experience as someone who builds a lot of Rust web services as: 1. My overall experience with async is very positive 2. There are tricky bits where even I, an experience borrow check wrestler, don't know what to do - I just refactor the code to avoid the issue in these cases. This is not a very common situation, it has only occurred in 'free time' code where I'm trying to really optimize my code. 3. I am overall very optimistic about the future of async in Rust, even if today it requires some onboarding time. I'm excited for things to improve. There are ergonomics wins coming soon like async in traits, there are improved compiler diagnostics, expansions of what can be done (to address my 'zero copy' use cases), etc. Perhaps it's bikeshedding but I hate the `= async` quite a lot. I'm curious to see how things develop from here in the next 3-5 years, as I imagine we'll see some significant improvements to the existing system.