>What does "native" mean, built into the language? Why does it matter?
I don't know how that macro works, but in kernel C bitfields are used in structs that map to device registers (that are mapped to memory).
>I suspect it's the same with type punning (though also, to some degree because we're still working out the details of what exactly the semantics of unsafe are.) In the end, you can always cast stuff to bytes and then cast those bytes to something else.
So if i want to store a series of things with random (length) types in a single array, i can ? Sounds like i can, even though you explained the simpler case.
>I don't take (too much) objection to that, and little with "not much more", but that doesn't mean that C has some secret stuff that only C can do, which it feels like you're implying.
And for the third (edit:second) time, that is not my point. Thing is that C does not have "secret stuff" and rust does. In C you get what you wrote, and not much more. There is no need for telling the compiler to not do some checking or to not make a copy of something. (edit2: granted, bitfields are not native to cpus as type punning is)
Rust, IMO, is more for the C++ crowd then C. And those two are very different.