I would guess that their stance is <i>&quot;If you care about that, do it yourself&quot;</i><p>IMO, that is the right attitude, given that moving fields around may interfere with how parts of large structures map to cache lines, and that may have huge performance impacts, if some parts of a structure are rarely accessed.<p>Yes, the compiler could try to optimize that, too, but saying that is a hard problem is an understatement, and it needs statistics that the compiler doesn&#x27;t have available. So, it definitely is unsuitable for go&#x27;s goal of fast compilation.