A handle to an established, reliable, datagram-oriented transport socket.

ReliableSocket is the interface for reading and writing datagrams over some underlying transport. All reads and writes operate using Buf objects, which represent views into some memory region specific to the socket. This makes zero-copy reads and writes possible, if the implementation chooses to support it.

Datagrams are delivered reliably and in order. If a packet cannot be delivered in order, the socket must close.

Any ReliableSocket can be implicitly converted to a Socket (by value, rvalue, or const reference).

The underlying socket begins established and open, but may close at any time. Once closed, all operations on the socket will report failures. A ReliableSocket cannot be reopened. A new one must be provisioned from a ReliableListener or a ReliableConnector.

A ReliableSocket is cheaply copyable and always safe to access, ensuring that the underlying socket state is valid as long as a handle is held. Users should drop their handles once no longer needed to ensure prompt resource reclamation.