Exonum do not support big-endian architectures about exonum HOT 5 CLOSED

@vldm, i assume this is covered now?

from exonum.

Why did you decide that? We use the byteorder crate and explicit conversions like LittleEndian::read_u32 and LittleEndian::write_u32 wherever the behavior between architectures may differ.

We must use a unified approach of -endianess for messages and storage data since it's protocol-specific behaviour and it is independent of the target architecture.

TLDR: The actual code should work on both architectures in the same way, but we did not test that.

Feel free to reopen issue.

from exonum.

@defuz yes, the code of u64/u16/u32 use byteorder::LittleEndian conversions, but SegmentFields slices, for example &[u64] &[u32] use transmute and Slice::from_raw which is not right way to represent architecture independent data.
@alekseysidorov reopen it pls

from exonum.

@defuz reopen plz.

from exonum.

@vldm You know what to do :)

from exonum.