-
Notifications
You must be signed in to change notification settings - Fork 428
Add support for async await #1205
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
Comments
Yes, we plan on adopting async await. We don't have anything for users to play around with yet though. |
swift-nio has already demo sources for support swift 5.5 and around this vapor has branch https://github.com/vapor/vapor/tree/async-await |
We now have an experimental release with initial support async/await https://github.com/grpc/grpc-swift/releases/tag/1.4.1-async-await.1 |
Thank you for the 1.4.1-async-await branch. Curious what the roadmap is. Specifically, are there plans for a 1.5.0-async-await branch? Do you anticipate this being folded in before 2.0? Thanks. |
Yes, we'll try to get that done soon.
Yes. The rough plan is to expose an async/await API alongside the existing API in a 1.x release so folks can move over to it if/when they choose. The next major version would drop the old API and keep just the async/await API as close as feasibly possible (at least for generated clients and service providers) in order to make migration from 1.x to 2.x less painful. With that in mind I'd like to leave this a little more time to let the current async/await APIs bake and also to improve test coverage. Feedback on APIs, usability and so on are always helpful so please let us know if you have any thoughts! |
Support for async await was added in the 1.8.0 release. |
Hi do you know where can I find the documentation about how to use async await on GRPC? |
This is probably the best place to start: https://github.com/grpc/grpc-swift/blob/main/docs/basic-tutorial.md |
are you planning to move to the "async-await" paradigm?
mb there is already some branch for tests?
The text was updated successfully, but these errors were encountered: