tag | 46f9a76c67ded38a28ac15f570ded962db791897 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Mon Oct 04 18:33:56 2021 -0700 |
object | 821d2a074bc11e3cd81c9156702d3ec6fb5f2228 |
Android 11.0.0 Release 46 (RQ3A.211001.001)
commit | 821d2a074bc11e3cd81c9156702d3ec6fb5f2228 | [log] [tgz] |
---|---|---|
author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Jan 06 17:11:57 2020 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Jan 06 17:11:57 2020 +0000 |
tree | fbc65879591dd214359807735838c3d9fa73b085 | |
parent | 666b4679235fbd8a2024626abee625267a8fce29 [diff] | |
parent | 38c3e288c6aae8e4fa4682a40f85bcf97eaa8f8e [diff] |
Allow warnings to migrate to rustc-1.40.0 am: 7a6bcadee4 am: 9a726a08d1 am: 38c3e288c6 Change-Id: I39a53f60e3e1601e509f2ed384b47d16773a8ea6
This crate provides convenience methods for encoding and decoding numbers in either big-endian or little-endian order.
Dual-licensed under MIT or the UNLICENSE.
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:
extern crate byteorder; 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
cratesThis 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 }
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.