tag | c107e6a696af24dc1e9065773f6c9b1390872d65 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Wed Dec 06 19:56:25 2023 -0800 |
object | 411aec5a6342d536e3f9c1a7a14a36c81e9ea6e0 |
aml_doc_341112000 (10760659,com.google.android.documentsui,com.google.android.go.documentsui)
commit | 411aec5a6342d536e3f9c1a7a14a36c81e9ea6e0 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Jul 07 04:50:17 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Jul 07 04:50:17 2023 +0000 |
tree | 2e4fcf8cb0393566c83c3292c845b3b95c86afac | |
parent | 5c5cd23e5c6d8553bc4ad9befa2a3a18ae19a3dd [diff] | |
parent | aed99d21caec70de07c009c76262620e16934c0a [diff] |
Snap for 10453563 from aed99d21caec70de07c009c76262620e16934c0a to mainline-documentsui-release Change-Id: I42ce72296e79f7e483e93ff1c279cfcc57a2b38a
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.