enet4 / byteordered Goto Github PK

Since this crate is envisioned as an extension to byteorder, should this crate just re-export all members of its public API, or keep it as a public module, as it currently is?

This issue is to discuss whether read/write methods should stay in the Endianness enum alone or we should also provide a monadic abstraction EndianReader/EndianWriter which would contain a source T and the intended byte order, so that one could write code like this:

let src = EndianReader::new(src, Endianness::Little);
let x = src.read_u32()?;

Hi,

This crate looks like exactly what we need in zbus but looks like this maybe unmaintained. @Enet4 could you please let me know about the status?

byteorder also provides methods for reading values into a slice (see e.g. #read_u16_into). It would be nice to have them in ByteOrdered as well.

• tests for writing via the base Endian types are missing
• not all methods in the ByteOrdered type are being tested