byteorder
byteorder copied to clipboard
Rust library for reading/writing numbers in big-endian and little-endian.
This eliminates four unsafe blocks by using methods from the standard library.
This updates the quickcheck tests for quickcheck version 1.0 with the patch https://github.com/BurntSushi/quickcheck/pull/278 applied.
This adds benchmarks of other crate methods that previously weren't benchmarked.
The documentation for `ByteOrder::write_int` says: > If n is not representable in nbytes, or if nbytes is > 8, then this method panics. However, passing inputs that fail the first...
I don't think this is a bug in `byteorder`. But I thought it demonstrates an interesting hazard that might be worth documenting for others. Some `byteorder::ReadBytesExt` methods rely on [`std::io::Read::read_exact`](https://doc.rust-lang.org/std/io/trait.Read.html#method.read_exact),...
[`std::io::Read::read_exact`](https://doc.rust-lang.org/std/io/trait.Read.html#method.read_exact) documentation says that if an error occurs, the state of the reader is unspecified: it may have consumed some number of bytes (between zero and the size of the...
There may be more that could be done with some deeper restructuring, but I figured I'd keep it simple to start with.
Hi, do you have any plan on supporting the [Read](https://github.com/rust-embedded/embedded-hal/blob/dd0bbbaa5c926628ff03dfd78fb54162fec05ab9/embedded-io/src/lib.rs#L304) and [Write](https://github.com/rust-embedded/embedded-hal/blob/dd0bbbaa5c926628ff03dfd78fb54162fec05ab9/embedded-io/src/lib.rs#L379) crates defined in [embedded-io](https://github.com/rust-embedded/embedded-hal/tree/master/embedded-io)? It would be great to be able to use this library in embedded systems...