Endian Trait

This crate provides a trait, Endian, which requires four methods for converting primitives with multi-byte representations between big- and little- endian orders. In addition to declaring the trait, this library implements it on Rust's primitives (bool, char, {i,u}{8,16,32,64,size}, f32, and f64).

An associated crate, endian_trait_derive, provides a custom-derive macro that will implement Endian for complex types that are composed of inner types which are themselves Endian.

The primary purpose of this library is to aid in the direct binary serialization of Rust types across machine boundaries. This is not a robust means of moving data across a network or filesystem, but it can be used as a basis for building stronger binary serialization procedures. Note that common transmission methods will also require implementing a conversion to/from byte arrays, which is beyond the scope of this library.

Usage

Require this crate (endian_trait) in your Cargo.toml, and the endian_trait_derive crate for access to the custom derive macro.

toml [dependencies] endian_trait = "0.2" endian_trait_derive = "0.2"

Import them in your crate root:

```rust extern crate endian_trait;

[macro_use]

extern crate endiantraitderive; ```

and then use the Endian trait to flip bytes.

```rust use endian_trait::Endian;

[derive(Endian)]

struct Foo { bar: i32, baz: f64, }

[derive(Endian)]

struct Quux { f: Foo, g: bool, }

let q = Quux { f: Foo { bar: 42, baz: 6.283185, }, g: true, }.to_be();

let q2: Quux = q.from_be(); ```

Useful ... Usage

Endian conversions destroy the utility, and in some cases (floats, chars) the validity, of the data on which they are performed. Once data is transformed away from local endian, it can no longer be used as anything but a bare sequence of bytes with no further meaning. Similarly, the transformations from an order to local endian are only useful to perform on a sequence of bytes that are known to be in the right shape.

This trait is thus only useful when coupled with binary serialization methods such as Into<[u8; N]> and From<[u8; N]>.

In my projects that use this, I have the following workflow for binary ser/des:

```rust

[derive(Endian)]

struct Foo { // ... } impl From<[u8; N]> for Foo { fn from(src: [u8; N]) -> Self { // ... } } impl Into<[u8; N]> for Foo { fn into(self) -> [u8; N] { // ... } }

let f: Foo = makeafoo(); let fbytes: [u8; N] = f.to_be().into();

let rawfoo: [u8; N] = readfromnetwork(); let buildfoo: Foo = Foo::from(rawfoo).frombe(); ```

Do keep in mind that once data is converted to a transport endian order, it can no longer be considered as anything but a collection of bytes. Converting a char or float will almost always result in a bit pattern that is invalid to be read as its stated type, and will remain so until converted back to native order on the other side. The From and Into impls used for binary ser/des should just be transmutes and byte shunts, as they will be likely working with data that is the correct width but of logically invalid form.

You could also move the endian conversions into the From/Into methods, but I personally prefer keeping those uncoupled.

There's really no other reason to use this trait, as far as I'm aware.