-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ClientCallable.call() signature #23
Comments
Sure |
Probably |
No you're right, that makes more sense. Thanks! |
On this note, is there a way to pass the ExecutionContext explicitly to call? |
Not unless we change the signature =P Which nobody has done yet... |
#57 closes this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a bit of a nitpick but when
call()
is expanded it includes a call toFuture.map
which requires an execution context. My IDE kept deleting the import because it didn't know it needed it. Would it be possible to change the signature ofcall()
to something likecall(implicit executor: ExecutionContext)
?The text was updated successfully, but these errors were encountered: