Proposal: shall we use `async_fn_in_traits`? about volo HOT 4 OPEN

I've tried this, but seems we have encountered the Send bound problem in volo.

I will try again some time later when this feature is more mature.

from volo.

After using async_fn_in_traits, will we be able to provide msrv?

from volo.

@my-vegetable-has-exploded Yes, this will be a breaking change, we are discussing and testing the new design.
Long story short, we are going to change Service to something like this:

pub trait Service<Cx, Request> {
 /// Responses given by the service.
 type Response;
 /// Errors produced by the service.
 type Error;
 /// Process the request and return the response asynchronously.
 fn call<'cx, 's>(&'s self, cx: &'cx mut Cx, req: Request) -> impl Future<Output = Result<Self::Response, Self::Error>> + Send + 'cx
 where
 's: 'cx;
}

But we are not quite sure if this works fine, so we need some more tests.

from volo.

We met this issue rust-lang/rust#100013 when migrating to rpitit, maybe we need to wait for this bug to be fixed.

from volo.