Future returned by `Serve::serve()` is not `Send` about tarpc HOT 11 OPEN

Hi, thanks for raising this issue! In the example service, it does spawn the serve futures. Any idea what's different in yours? I suspect the issue is that your code is trying to be generic over multiple services?

from tarpc.

Yes, it is because I'm trying to make a generic function. Although in all generated trait implementations, the future returned by serve() are Send, the signature of serve() itself does not require that. So merely by looking at Serve, the compiler cannot decide whether or not the future is Send.

from tarpc.

How large of a library are you writing that is generic over tarpc service functions? And how many tarpc services do you expect to use the library? I'm trying to gauge whether it'd be practical to just write the code once per service.

from tarpc.

Writing code for each service indeed would work for me. I only have two concrete service type to support.

Feel free to close as "working as intended".

from tarpc.

Thanks for the details! I'll keep this issue open, because I would like to fix it eventually, potentially just waiting for Rust to offer a more complete solution.

from tarpc.

@tikue what do you think about adding in trait-variant? It fixes this use case (I tested it in my fork), and is officially suggested by the Rust lang team.

Only hiccup is that usage of that macro would conflict with this blanket impl, which I'm not sure of a solution too without specialization or negative bounds.

I'm happy to work through a PR 🙂

from tarpc.