The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#) https://grpc.io/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Esun Kim decc199ca8 Fix by clang-tidy 4 years ago
..
README.md Justify existence of this directory 4 years ago
atm.h clang-format 7 years ago
atm_gcc_atomic.h clang-format 7 years ago
atm_gcc_sync.h Add GPR_ATM_INC_ADD_THEN to grpc_core::RefCount 6 years ago
atm_windows.h Fix by clang-tidy 4 years ago
byte_buffer.h Fix readability-inconsistent-declaration-parameter-name manually 4 years ago
byte_buffer_reader.h Revert API changes to byte buffer reader 5 years ago
compression_types.h Clarify compression algorithm enum order 6 years ago
connectivity_state.h Assume that subchannels start in state IDLE. 7 years ago
fork.h Resolve Swift warnings by specifying void arguments 7 years ago
gpr_slice.h auto-fix most of licenses 8 years ago
gpr_types.h some typo errors 6 years ago
grpc_types.h Fix by clang-tidy 4 years ago
log.h Added grpc_stacktrace_minloglevel 4 years ago
port_platform.h Revert "Enable GPR_ABSEIL_SYNC on Apple" 4 years ago
propagation_bits.h auto-fix most of licenses 8 years ago
slice.h grpc_slice_refcount devirtualization 6 years ago
status.h docs: add note about retrying UNAVAILABLE 6 years ago
sync.h Added abseil-based sync 5 years ago
sync_abseil.h Added abseil-based sync 5 years ago
sync_custom.h Add a sanity check for inclusion of port_platform.h 7 years ago
sync_generic.h fix typo in document 5 years ago
sync_posix.h 1) remove unnecessary initialization; 6 years ago
sync_windows.h Fix by clang-tidy 4 years ago

README.md

Welcome to include/grpc/impl/codegen

Why is this directory here?

This directory exists so that generated C++ code can include selected files upon which it depends without having to depend on the entire gRPC C++ library. This directory thus exists to support include/grpcpp/impl/codegen. This constraint is particularly relevant for users of bazel, particularly if they use the multi-lingual proto_library target type. Generated code that uses this target only depends on the gRPC C++ targets associated with these header files, not the entire gRPC C++ codebase since that would make the build time of these types of targets excessively large (particularly when they are not even C++ specific).

What should user code do?

User code should not include anything from this directory. Only generated code and gRPC library code should include contents from this directory. C++ user code should instead include contents from the main grpcpp directory or its accessible subcomponents like grpcpp/support. It is possible that we may remove this directory altogether if the motivations for its existence are no longer strong enough (e.g., if the gRPC C++ library no longer has a need for an impl/codegen directory of its own).