Google GitGoogle Git
Sign in
android/platform/external/grpc-grpc/8bbd11ebed
commit
8bbd11ebedc58f5670d781bbd304b75f1f53324d
[log]
author
Craig Tiller <ctiller@google.com>
Tue Aug 15 21:44:13 2023 -0700
committer
GitHub <noreply@github.com>
Tue Aug 15 21:44:13 2023 -0700
tree
442912bb35dc3857a4458a42ea04b9b041ad80e6
parent
4d24b93cbbcad9c4974dab05a0f5a524fdd35a04 [diff]
[promises] New `Join`, `TryJoin` implementation (#33995)

Our current implementation of Join, TryJoin leverage some complicated
template stuff to work, which makes them hard to maintain. I've been
thinking about ways to simplify that for some time and had something
like this in mind - using a code generator that's at least a little more
understandable to code generate most of the complexity into a file that
is checkable.

Concurrently - I have a cool optimization in mind - but it requires that
we can move promises after polling, which is a contract change. I'm
going to work through the set of primitives we have in the coming weeks
and change that contract to enable the optimization.

---------

Co-authored-by: ctiller <ctiller@users.noreply.github.com>
17 files changed
tree: 442912bb35dc3857a4458a42ea04b9b041ad80e6
  1. .bazelci/
  2. .github/
  3. bazel/
  4. cmake/
  5. doc/
  6. etc/
  7. examples/
  8. fuzztest/
  9. include/
  10. spm-core-include/
  11. spm-cpp-include/
  12. src/
  13. summerofcode/
  14. templates/
  15. test/
  16. third_party/
  17. tools/
  18. .bazelignore
  19. .bazelrc
  20. .clang-format
  21. .clang-tidy
  22. .dockerignore
  23. .editorconfig
  24. .git-blame-ignore-revs
  25. .gitallowed
  26. .gitattributes
  27. .gitignore
  28. .gitmodules
  29. .istanbul.yml
  30. .pylintrc
  31. .pylintrc-examples
  32. .pylintrc-tests
  33. .rspec
  34. .yapfignore
  35. .yardopts
  36. _metadata.py
  37. AUTHORS
  38. black.toml
  39. BUILD
  40. build_autogenerated.yaml
  41. build_config.rb
  42. build_handwritten.yaml
  43. BUILDING.md
  44. CMakeLists.txt
  45. CODE-OF-CONDUCT.md
  46. composer.json
  47. CONCEPTS.md
  48. config.m4
  49. config.w32
  50. CONTRIBUTING.md
  51. Gemfile
  52. GOVERNANCE.md
  53. gRPC-C++.podspec
  54. gRPC-Core.podspec
  55. gRPC-ProtoRPC.podspec
  56. gRPC-RxLibrary.podspec
  57. grpc.bzl
  58. grpc.def
  59. grpc.gemspec
  60. grpc.gyp
  61. gRPC.podspec
  62. LICENSE
  63. MAINTAINERS.md
  64. Makefile
  65. MANIFEST.md
  66. NOTICE.txt
  67. OWNERS
  68. Package.swift
  69. package.xml
  70. PYTHON-MANIFEST.in
  71. Rakefile
  72. README.md
  73. requirements.bazel.txt
  74. requirements.txt
  75. SECURITY.md
  76. setup.cfg
  77. setup.py
  78. TROUBLESHOOTING.md
  79. WORKSPACE
README.md

gRPC – An RPC library and framework

gRPC is a modern, open source, high-performance remote procedure call (RPC) framework that can run anywhere. gRPC enables client and server applications to communicate transparently, and simplifies the building of connected systems.

Join the chat at https://gitter.im/grpc/grpc

To start using gRPC

To maximize usability, gRPC supports the standard method for adding dependencies to a user‘s chosen language (if there is one). In most languages, the gRPC runtime comes as a package available in a user’s language package manager.

For instructions on how to use the language-specific gRPC runtime for a project, please refer to these documents

  • C++: follow the instructions under the src/cpp directory
  • C#/.NET: NuGet packages Grpc.Net.Client, Grpc.AspNetCore.Server
  • Dart: pub package grpc
  • Go: go get google.golang.org/grpc
  • Java: Use JARs from Maven Central Repository
  • Kotlin: Use JARs from Maven Central Repository
  • Node: npm install @grpc/grpc-js
  • Objective-C: Add gRPC-ProtoRPC dependency to podspec
  • PHP: pecl install grpc
  • Python: pip install grpcio
  • Ruby: gem install grpc
  • WebJS: follow the grpc-web instructions

Per-language quickstart guides and tutorials can be found in the documentation section on the grpc.io website. Code examples are available in the examples directory.

Precompiled bleeding-edge package builds of gRPC master branch's HEAD are uploaded daily to packages.grpc.io.

To start developing gRPC

Contributions are welcome!

Please read How to contribute which will guide you through the entire workflow of how to build the source code, how to run the tests, and how to contribute changes to the gRPC codebase. The “How to contribute” document also contains info on how the contribution process works and contains best practices for creating contributions.

Troubleshooting

Sometimes things go wrong. Please check out the Troubleshooting guide if you are experiencing issues with gRPC.

Performance

See the Performance dashboard for performance numbers of master branch daily builds.

Concepts

See gRPC Concepts

About This Repository

This repository contains source code for gRPC libraries implemented in multiple languages written on top of a shared C core library src/core.

Libraries in different languages may be in various states of development. We are seeking contributions for all of these libraries:

LanguageSource
Shared C [core library]src/core
C++src/cpp
Rubysrc/ruby
Pythonsrc/python
PHPsrc/php
C# (core library based)src/csharp
Objective-Csrc/objective-c
LanguageSource repo
Javagrpc-java
Kotlingrpc-kotlin
Gogrpc-go
NodeJSgrpc-node
WebJSgrpc-web
Dartgrpc-dart
.NET (pure C# impl.)grpc-dotnet
Swiftgrpc-swift