> I always understood the native types to be the "probably most efficient" choice Both of int32_t on Windows and int64_t on Unixes can't be the "probably most

> I always understood the native types to be the "probably most efficient" choice Both of int32_t on Windows and int64_t on Unixes can't be the "probably most efficient" choice on the same machine. Besides, struct bloating is a perfectly fine C optimization that your compile can do at any time to get the most efficient implementation without that "probably" part. It almost never does, tough, because it's a shitty operation and because CPUs that handle 64 bits perfectly but fumble around with 32 bits are a historic oddity only.