Name |
Date |
Size |
#Lines |
LOC |
||
---|---|---|---|---|---|---|
.. | - | - | ||||
README.md | H A D | 25-Apr-2025 | 1.2 KiB | 23 | 18 | |
atm.h | H A D | 25-Apr-2025 | 899 | 30 | 5 | |
atm_gcc_atomic.h | H A D | 25-Apr-2025 | 943 | 30 | 5 | |
atm_gcc_sync.h | H A D | 25-Apr-2025 | 935 | 30 | 5 | |
atm_windows.h | H A D | 25-Apr-2025 | 931 | 30 | 5 | |
byte_buffer.h | H A D | 25-Apr-2025 | 893 | 30 | 5 | |
byte_buffer_reader.h | H A D | 25-Apr-2025 | 921 | 30 | 5 | |
compression_types.h | H A D | 25-Apr-2025 | 984 | 31 | 5 | |
connectivity_state.h | H A D | 25-Apr-2025 | 981 | 31 | 5 | |
fork.h | H A D | 25-Apr-2025 | 865 | 30 | 5 | |
gpr_types.h | H A D | 25-Apr-2025 | 948 | 31 | 5 | |
grpc_types.h | H A D | 25-Apr-2025 | 949 | 31 | 5 | |
log.h | H A D | 25-Apr-2025 | 874 | 30 | 5 | |
port_platform.h | H A D | 25-Apr-2025 | 868 | 28 | 4 | |
propagation_bits.h | H A D | 25-Apr-2025 | 918 | 30 | 5 | |
slice.h | H A D | 25-Apr-2025 | 879 | 30 | 5 | |
status.h | H A D | 25-Apr-2025 | 873 | 30 | 5 | |
sync.h | H A D | 25-Apr-2025 | 904 | 30 | 5 | |
sync_abseil.h | H A D | 25-Apr-2025 | 932 | 30 | 5 | |
sync_custom.h | H A D | 25-Apr-2025 | 932 | 30 | 5 | |
sync_generic.h | H A D | 25-Apr-2025 | 936 | 30 | 5 | |
sync_posix.h | H A D | 25-Apr-2025 | 928 | 30 | 5 | |
sync_windows.h | H A D | 25-Apr-2025 | 936 | 30 | 5 |
README.md
1# Welcome to `include/grpc/impl/codegen` 2 3## Why is this directory here? 4 5This directory exists so that generated C++ code can include selected files upon 6which it depends without having to depend on the entire gRPC C++ library. This 7directory thus exists to support `include/grpcpp/impl/codegen`. This constraint 8is particularly relevant for users of bazel, particularly if they use the 9multi-lingual `proto_library` target type. Generated code that uses this target 10only depends on the gRPC C++ targets associated with these header files, not the 11entire gRPC C++ codebase since that would make the build time of these types of 12targets excessively large (particularly when they are not even C++ specific). 13 14## What should user code do? 15 16User code should *not* include anything from this directory. Only generated code 17and gRPC library code should include contents from this directory. C++ user code 18should instead include contents from the main `grpcpp` directory or its 19accessible subcomponents like `grpcpp/support`. It is possible that we may 20remove this directory altogether if the motivations for its existence are no 21longer strong enough (e.g., if the gRPC C++ library no longer has a need for an 22`impl/codegen` directory of its own). 23