abrasion/third_party/cargo/vendor/byteorder-1.4.3
q3k 4a50bbf00d third_party/cargo: re-raze, fix winapi for windows 2021-05-03 23:43:36 +02:00
..
benches third_party/cargo: update 2021-04-03 16:13:10 +00:00
src third_party/cargo: update 2021-04-03 16:13:10 +00:00
.cargo-checksum.json third_party/cargo: update 2021-04-03 16:13:10 +00:00
BUILD.bazel third_party/cargo: re-raze, fix winapi for windows 2021-05-03 23:43:36 +02:00
CHANGELOG.md third_party/cargo: update 2021-04-03 16:13:10 +00:00
COPYING third_party/cargo: update 2021-04-03 16:13:10 +00:00
Cargo.toml third_party/cargo: update 2021-04-03 16:13:10 +00:00
LICENSE-MIT third_party/cargo: update 2021-04-03 16:13:10 +00:00
README.md third_party/cargo: update 2021-04-03 16:13:10 +00:00
UNLICENSE third_party/cargo: update 2021-04-03 16:13:10 +00:00
rustfmt.toml third_party/cargo: update 2021-04-03 16:13:10 +00:00

README.md

byteorder

This crate provides convenience methods for encoding and decoding numbers in either big-endian or little-endian order.

Build status

Dual-licensed under MIT or the UNLICENSE.

Documentation

https://docs.rs/byteorder

Installation

This crate works with Cargo and is on crates.io. Add it to your Cargo.toml like so:

[dependencies]
byteorder = "1"

If you want to augment existing Read and Write traits, then import the extension methods like so:

use byteorder::{ReadBytesExt, WriteBytesExt, BigEndian, LittleEndian};

For example:

use std::io::Cursor;
use byteorder::{BigEndian, ReadBytesExt};

let mut rdr = Cursor::new(vec![2, 5, 3, 0]);
// Note that we use type parameters to indicate which kind of byte order
// we want!
assert_eq!(517, rdr.read_u16::<BigEndian>().unwrap());
assert_eq!(768, rdr.read_u16::<BigEndian>().unwrap());

no_std crates

This crate has a feature, std, that is enabled by default. To use this crate in a no_std context, add the following to your Cargo.toml:

[dependencies]
byteorder = { version = "1", default-features = false }

Alternatives

Note that as of Rust 1.32, the standard numeric types provide built-in methods like to_le_bytes and from_le_bytes, which support some of the same use cases.