Nemo provides session type abstractions for asynchronous networking protocols. It can be used to build high performance, memory safe and type-safe protocol implementations.
Session types allow you to encode the description of a protocol in the type system. The goal is to ensure that two clients can never disagree about their state or expectations when communicating. Through session types, it is possible to define protocols that must be implemented properly -- your code simply will not compile otherwise.
Channels are implementations of
Peano numbers are natural numbers expressed as successions of zero. We use them in our API to provide "nested" protocol escaping, as you must indicate the number of layers you wish to escape from.
Session types encode the current state of a communication channel. It is not possible to change to another state without following the protocol.
Channels are provided to handlers to act as a "courier" for the session type and a guard for the IO backend.
Handlers must return
This trait is implemented by backing IO structures to offer an
interface for bi-directional channels. Discriminants are sent
and received by
An implementation of this trait provides sending and receiving