The crate that was promised to patch the limitations of 1.75 async trait fn (trait-variant) never took off and was never finished.
This leaves library developers that want to support both boxed and non-boxed futures in messy state since most need to do the impl Future to get the Send bound and thus can't use async-trait.
I am wondering if async-trait could support the return impl Future<Output = ...> + Send syntaxt to help in the transition? Or would that be a breaking change / not something you would want. Even just basic support would already be a huge improvements.
Hi!
The crate that was promised to patch the limitations of 1.75 async trait fn (trait-variant) never took off and was never finished.
This leaves library developers that want to support both boxed and non-boxed futures in messy state since most need to do the
impl Future
to get theSend
bound and thus can't use async-trait.I am wondering if async-trait could support the return
impl Future<Output = ...> + Send
syntaxt to help in the transition? Or would that be a breaking change / not something you would want. Even just basic support would already be a huge improvements.Thanks