Type and layout rules
Integer widths are fixed; aggregate and pointer layout comes from the selected target.
DByte 12.0 · Reference
Contract§
Every backend consumes the same canonical decisions.
Mechanics§
This reference ties canonical type identity to size, alignment, field order, pointer mutability, enum tag/payload and aggregate ABI. Layout is always parameterized by an explicit target.
Validation and failure§
No backend may assign a second representation, promote integer types through a new system or infer host-sized layout.
Evidence and boundary§
Inspect --layout snapshots and exact native field/array accesses provide both declarative and executable evidence.