Ah, I see! I didn't realize those were the types you meant.    We do need a better solution for bitfields, in-tree.    In the meantime, would you please add a comment to these types, explicitly saying to consider a more type-safe version before stabilizing? That way it doesn't get lost.