commit | 346fb1ed74cf9455b33f1e2a444c8ca0fc84a09f | [log] [tgz] |
---|---|---|
author | James Farrell <[email protected]> | Thu Aug 15 02:06:13 2024 +0000 |
committer | Automerger Merge Worker <[email protected]> | Thu Aug 15 02:06:13 2024 +0000 |
tree | a1745e75818229af6138aa83451ea788aacd3805 | |
parent | 5f36787c24d05395a4ded5af4834ddec7f5c0f50 [diff] | |
parent | 3c5d9a5298efd09e48a43b0ff4e931d5a20fb9a3 [diff] |
Migrate 25 crates to monorepo am: 95b1940dbc am: 3c5d9a5298 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/byteorder/+/3219321 Change-Id: Iabfedf5b70936fde553238ef16640e1cd3d6aea4 Signed-off-by: Automerger Merge Worker <[email protected]>
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:
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.