Encode, a Rust library for building encoders and serializers

Encoders/serializers made easy.

encode is a toolbox for building encoders and serializers in Rust. It is heavily inspired by the winnow and nom crates, which are used for building parsers. It is meant to be a companion to these crates, providing a similar level of flexibility and ease of use for reversing the parsing process.

The main idea behind encode is to provide a set of combinators for building serializers. These combinators can be used to build complex encoders from simple building blocks. This makes it easy to build encoders for different types of data, without having to write a lot of boilerplate code.

Another key feature of encode is its support for no_std environments. This makes it suitable for use in embedded systems, where the standard library (and particularly the [std::io] module) is not available.

See the examples folder for some examples of how to use encode. Also, check the [combinators] module for a list of all the combinators provided by the crate.

Feature highlights

• #![no_std] compatible
• #![forbid(unsafe_code)]
• Simple and flexible API
• Minimal dependencies
• Ready to use combinators for minimizing boilerplate.

Cargo features

• default: Enables the std feature.
• std: Enables the use of the standard library.
• alloc: Enables the use of the alloc crate.
• arrayvec: Implements [Encodable] for [arrayvec::ArrayVec].

FAQs

Why the Encoder trait instead of bytes::BufMut?

From bytes documentation

A buffer stores bytes in memory such that write operations are infallible. The underlying storage may or may not be in contiguous memory. A BufMut value is a cursor into the buffer. Writing to BufMut advances the cursor position.

The bytes crate was never designed with falible writes nor no_std targets in mind. This means that targets with little memory are forced to crash when memory is low, instead of gracefully handling errors.

Why the Encoder trait instead of std::io::Write?

Because it's not available on no_std

Why did you build this?

• Because there is no alternative, at least that i know of, that supports no_std properly
• Because it easily lets you create TLV types
• Because it's easier to work with than std::io::Write and std::fmt::Write
• Because using format_args! with binary data often leads to a lot of boilerplate