I love Rust, but async is a hot mess and you cannot just write async code the same way that you write sync code. I'm getting more convinced that mixing the two is a bad idea, and that Go's approach of making everything sync with a single async channel primitive might be right.

I'm currently plumbing through some logic to call a sync method on a struct that implements Future and it's... an interesting challenge.

While we can make zero-cost async abstractions somewhat easy for users, the library developers are the ones who suffer the pain.