Before history rewrite
Go to file
Ty Overby f4c5c7b86d Merge branch 'master' of github.com:TyOverby/bincode 2017-01-31 10:20:18 -08:00
examples moved the two designs into modules 2015-08-07 17:35:27 -07:00
src Update to serde 0.9.X (#93) 2017-01-31 09:59:29 -08:00
tests Update to serde 0.9.X (#93) 2017-01-31 09:59:29 -08:00
.gitignore rustup 2015-03-25 15:50:41 -07:00
.travis.yml Add cargo features for rustc-serialize and serde (#70) 2016-04-15 11:03:32 -07:00
Cargo.toml Merge branch 'master' of github.com:TyOverby/bincode 2017-01-31 10:20:18 -08:00
LICENSE.md Update LICENSE.md 2014-09-18 13:30:55 -07:00
README.md update example in readme 2015-08-12 20:16:30 -07:00
logo.png add logo 2015-02-15 12:36:44 -08:00
readme.dev.md Added Crates.io badge 2015-04-16 14:43:07 -07:00

README.md

Bincode

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 functions 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

extern crate bincode;
extern crate rustc_serialize;

use bincode::SizeLimit;
use bincode::rustc_serialize::{encode, decode};

#[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> = 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 = decode(&encoded[..]).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:

  • isize/usize are encoded as i64/u64, for portability.
  • enums variants are encoded as a u32 instead of 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.