Struct Padding Syntax - Would this work?

Most of us already seen classic reserved0, reverved1, reserved23 or even unknown1 etc The thing is, that in many scenarios when it comes to extern structs with C-ABI interop we do not implement the struct fully or in some cases we can’t fully implement the struct, so at the end we end-up with struct full of reserved or unknown fields that has numerical sufix, since we already have a discard syntax and we also do have non-exhaustive enum, why not adding padding syntax to structs, might even wor...