There is one thing I think needs to be addressed following #74: usize is dependent on the architecture and is used in the serde implementation. I"d like to get that sorted out before anything public is released.

There is one thing I think needs to be addressed following #74: usize is dependent on the architecture and is used in the serde implementation. I"d like to get that sorted out before anything public is released.

I see. You mean the serialized data is incompatible before and after the u32 -> usize change, right?

That"s true, but I"m more concerned with portability of serialized data from one architecture to another.

yes, need to create custom serialize mod which also makes endianness correct.

Current implementation is not portable, maybe we should define the serialized format first. add an endian flag to the data, or serialize data to [u8]?

@james7132 if this is a release blocker, how about hide the usize as a opt in feature?

0.5.0 has been published.