Go to file
Ty cb0ef826f9 Merge pull request #14 from TyOverby/better-errors
More robust and precise error handling.
2015-01-07 22:05:12 -08:00
examples added size-limits to all functions. Currently the size limits aren't actually enforced. 2015-01-05 11:19:08 -08:00
src More robust and precise error handling. 2015-01-08 04:02:19 +01:00
.gitignore compiles without any features 2014-09-15 13:59:11 -07:00
.travis.yml compiles without any features 2014-09-15 13:59:11 -07:00
Cargo.toml Use latest rustc-serialize 2015-01-07 19:30:14 +01:00
LICENSE.md Update LICENSE.md 2014-09-18 13:30:55 -07:00
README.md Document some encoding details 2015-01-07 03:49:19 +01:00
readme.dev.md changed project name to 'bincode' 2014-10-27 09:45:24 -07:00

README.md

Binary Encoder / Decoder

Build Status

A compact encoder / decoder pair that uses an binary zero-fluff encoding scheme. The size of the encoded object will be the same or smaller than the size that the object takes up in memory in a running Rust program.

In addition to exposing two simple funcitons that encode to Vec and decode from Vec, binary-encode exposes a Reader/Writer API that makes it work perfectly with other stream-based apis such as rust files, network streams, and the flate2-rs compression library.

Api Documentation

Example

#![feature(old_orphan_check)]

extern crate bincode;
extern crate "rustc-serialize" as rustc_serialize;

use bincode::SizeLimit;

#[derive(RustcEncodable, RustcDecodable, PartialEq)]
struct Entity {
    x: f32,
    y: f32,
}

#[derive(RustcEncodable, RustcDecodable, PartialEq)]
struct World {
    entities: Vec<Entity>
}

fn main() {
    let world = World {
        entities: vec![Entity {x: 0.0, y: 4.0}, Entity {x: 10.0, y: 20.5}]
    };

    let encoded: Vec<u8> = bincode::encode(&world, SizeLimit::Infinite).unwrap();
    // 8 bytes for the length of the vector, 4 bytes per float.
    assert_eq!(encoded.len(), 8 + 4 * 4);
    let decoded: World = bincode::decode(encoded, SizeLimit::Infinite).unwrap();

    assert!(world == decoded);
}

Details

The encoding (and thus decoding) proceeds unsurprisingly -- primitive types are encoded according to the underlying Writer, tuples and structs are encoded by encoding their fields one-by-one, and enums are encoded by first writing out the tag representing the variant and then the contents.

However, there are some implementation details to be aware of:

  • int/uint are encoded as i64/u64, for portability.
  • enums variants are encoded as a u32 instead that as a uint. u32 is enough for all practical uses.
  • str is encoded as (u64, &[u8]), where the u64 is the number of bytes contained in the encoded string.