Devil is in the details but the async pathways are still new and lightly used. I’d be surprised if we can do it all without any breaking changes… — Try to avoid them, and doc them if we can’t, or similar.
I feel like if we could land @fcurella’s async cursor work, a lot would simplify here. (The existing a methods call the sync equivalent at bottom because there’s no option to do otherwise.) I’ve been pondering putting that into a third-party package, so we can at least play with it properly. 