Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
I'm a little confused. It seems to me that this wraps the endian-aware types so perfectly that there is not an effective difference between ulittle32_t and uint32_t.
Comment Actions
The difference is that without this patch, the following does not compile:
ulittle32_t X;
IO.mapRequired("u32", X);
Sure, I could map it to a uint32_t, but all my internal data structures are
represented with iendian aware types, so this allows me to interact with
existing code more cleanly
Comment Actions
OK. So the actual use case is not:
ulittle32_t X;
but:
type_embedded_with_ulittle32 X;
?
If so, LGTM
Comment Actions
Essentially. One concrete example is vector<ulittle32_t>, without this
patch it's very onerous to create one of these