The Rust MessagePack Library
RMP is a pure Rust MessagePack implementation of an efficient binary serialization format. This crate provides low-level core functionality, writers and readers for primitive values with direct mapping between binary MessagePack format.
Warning this library is still in rapid development and everything may change until 1.0 comes.
rmp, first add this to your
 = "^0.8"
RMP is designed to be lightweight and straightforward. There are low-level API, which gives you full control on data encoding/decoding process and makes no heap allocations. On the other hand there are high-level API, which provides you convenient interface using Rust standard library and compiler reflection, allowing to encode/decode structures using
Zero-copy value decoding
RMP allows to decode bytes from a buffer in a zero-copy manner easily and blazingly fast, while Rust static checks guarantees that the data will be valid until buffer lives.
Clear error handling
RMP's error system guarantees that you never receive an error enum with unreachable variant.
Robust and tested
This project is developed using TDD and CI, so any found bugs will be fixed without breaking existing functionality.
This crate represents the very basic functionality needed to work with MessagePack format. Ideologically it is developed as a basis for building high-level abstractions.
Currently there are two large modules: encode and decode. More detail you can find in the corresponding sections.
Formally every MessagePack message consists of some marker encapsulating a data type and the
data itself. Sometimes there are no separate data chunk, for example for booleans. In these
cases a marker contains the value. For example, the
true value is encoded as
let mut buf = Vecnew; write_bool.unwrap; assert_eq!;
Sometimes a single value can be encoded in multiple ways. For example a value of
42 can be
[0x2a], [0xcc, 0x2a], [0xcd, 0x00, 0x2a] and so on, and all of them are
considered as valid representations. To allow fine-grained control over encoding such values
the library provides direct mapping functions.
let mut bufs = vec!; write_pfix.unwrap; write_u8.unwrap; write_u16.unwrap; write_u32.unwrap; write_u64.unwrap; assert_eq!; assert_eq!; assert_eq!; assert_eq!; assert_eq!;
But they aren't planned to be widely used. Instead we often need to encode bytes compactly to save space. In these cases RMP provides functions that guarantee that for encoding the most compact representation will be chosen.
let mut buf = Vecnew; write_sint.unwrap; assert_eq!;
On the other hand for deserialization it is not matter in which representation the value is encoded - RMP deals with all of them.
Sometimes you know the exact type representation and want to enforce the deserialization process to make it strongly type safe.
let buf = ; assert_eq!;
However if you try to decode such bytearray as other integer type, for example
u32, there will
be type mismatch error.
let buf = ; read_u32.err.unwrap;
But sometimes all you want is just to encode an integer that must fit in the specified type
no matter how it was encoded. RMP provides
such function to ease integration with
other MessagePack libraries.
let buf = ; assert_eq!; assert_eq!; assert_eq!; assert_eq!; assert_eq!; assert_eq!;
Almost all API are represented as pure functions, which accepts a generic
the value to be encoded/decoded. For example let's do a round trip for π number.
let pi = PI; let mut buf = Vecnew; write_f64.unwrap; assert_eq!; assert_eq!;