Atomic Read-Only Iobuf An `ROIobuf` which is safe to `Send` across tasks and `Share` with other tasks. This atomically refcounts the buffer, which ha

Used to provide custom memory to Iobufs, instead of just using the heap.

Append-Only Input Buffer This buffer is intended to act as a intermediate buffer to be `fill`ed by incoming streaming data, such as sockets, files, o

Each leaf of this enum is tagged with the allocation length listed in the header.

A ring buffer implemented with `Iobuf`s.

8-64 bit integer types. Not floating point. This used to be in the standard library, but was pulled out into an external library that adds support fo

Input/Output Buffer Have your functions take a generic IObuf when they don't modify the buffer contents. This allows them to be used with both `ROIob

Read-Only Iobuf An `Iobuf` that cannot write into the buffer, but all read-only operations are supported. It is possible to get a `RWIobuf` by perfor

Read-Write Iobuf An `Iobuf` which can read and write into a buffer. Iobufs may be `cloned` cheaply. When cloned, the data itself is shared and refco

A `RawIobuf` is the representation of both a `RWIobuf` and a `ROIobuf`. It is very cheap to clone, as the backing buffer is shared and refcounted.

An iterator over references to buffers inside a `BufSpan`.

A moving iterator over buffers inside a `BufSpan`.

A unique, immutable Iobuf. If the refcount on an Iobuf is `1`, it can be made unique with `.unique()`. This will allow sending across channels, and l