@david_chisnall@infosec.exchange
Post #3788836
2026-07-13 08:21 UTC
@zwol@masto.hackers.town I don’t think that’s the right layer to solve this. As you say, to be useful it would require annotation in source languages and, if you have that, the compiler can insert byte swapping as required. Erlang, for example, does this very nicely.
Replies (1)
-
@zwol@masto.hackers.town 2026-07-13 15:38
@david_chisnall@infosec.exchange It might help to understand where I'm coming from if you know that at my job (which is an almost exclusively Python shop and we deal with a lot of historical scientific data that was archived big-endian) it is regularly a problem for me that NumPy exposes the endianness of data on disk to the programmer *without* also giving them the necessary tools to handle it efficiently. You wind up copying entire multi-GB data blocks just to byteswap them.