The intent of a specification is to be explicit, and in doing so it's poor form to say "this is undefined, so we're simply not going to mention it in the spec at all". If it's undefined then the spec should say so, especially if the alternative is for one to cast about in confusion until hopefully stumbling across the relevant documentation in, of all places, the bug tracker.
> It seems fine to me for the spec not to guarantee anything about struct field order in memory. The spec doesn't operate at that level.
And while he adds
> That said, no Go compiler should probably ever reorder struct fields.
the final result is struct memory layout is unspecified and implementation-dependent (essentially identical to repr(rust), as I understand it)