alt Hacker NewsWhat does it actually cost you to define a macro which is a no-op on little endian architectures and then use it at the point of serialization/deserialization?
What does it actually cost you to define a macro which is a no-op on little endian architectures and then use it at the point of serialization/deserialization?
A lot because to the compiler a no-op macro is the same as not having the macro in the same place so it won’t catch cases where you should use the macro but didn’t. Then you just give yourself a false sense of security unless you actually test on big endian.