You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 16, 2020. It is now read-only.
I'm running into a lot of trouble when trying to pass a client to a function. It looks like the accepting function needs to have very specific bounds on the client type in order for it to match the generated bounds on the client's RPC functions.
Though it is an interesting idea, if the client could generate a trait... It'd be nicer to be generic over T: Greeter than Greeter<T> with T: GrpcService<R>...
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Migrating discussion from here.
I'm running into a lot of trouble when trying to pass a client to a function. It looks like the accepting function needs to have very specific bounds on the client type in order for it to match the generated bounds on the client's RPC functions.
Minimal reproduction:
https://github.com/GeorgeHahn/tower-grpc/blob/pass-client-to-fn/tower-grpc-examples/src/helloworld/client.rs#L60
Generates the following client in
helloworld.rs
:Am I thinking about this wrong? My gut feeling is that a generated client trait would help solve this cleanly.
The text was updated successfully, but these errors were encountered: