Go to the source code of this file.
#define GRPC_SLICE_BUFFER_INLINE_ELEMENTS 8 |
#define GRPC_SLICE_INLINED_SIZE (sizeof(size_t) + sizeof(uint8_t *) - 1) |
#define GRPC_SLICE_LENGTH |
( |
|
slice | ) |
|
Value:((slice).refcount ? (slice).data.refcounted.length \
: (slice).data.inlined.length)
#define GRPC_SLICE_SET_LENGTH |
( |
|
slice, |
|
|
|
newlen |
|
) |
| |
Value:((slice).refcount ? ((slice).data.refcounted.length = (size_t)(newlen)) \
: ((slice).data.inlined.length = (uint8_t)(newlen)))
#define GRPC_SLICE_START_PTR |
( |
|
slice | ) |
|
Value:((slice).refcount ? (slice).data.refcounted.bytes \
: (slice).data.inlined.bytes)
Reference count container for grpc_slice.
Contains function pointers to increment and decrement reference counts. Implementations should cleanup when the reference count drops to zero. Typically client code should not touch this, and use grpc_slice_malloc, grpc_slice_new, or grpc_slice_new_with_len instead.
Slice API.
A slice represents a contiguous reference counted array of bytes. It is cheap to take references to a slice, and it is cheap to create a slice pointing to a subset of another slice.
The data-structure for slices is exposed here to allow non-gpr code to build slices from whatever data they have available.
When defining interfaces that handle slices, care should be taken to define reference ownership semantics (who should call unref?) and mutability constraints (is the callee allowed to modify the slice?)