@mdempsky That's an ok choice too, but I like to keep a version around that shows that there's no need to waste space in internal fragmentation (which is currently the case for gc-aligned structs used inside arrays or other structs).
The current StdSizes most closely matches
the gc compiler, and the uses I know of that care
which compiler the sizes are for are all for
the gc compiler, so call the existing
Run-TryBot: Josh Bleecher Snyder <email@example.com>
TryBot-Result: Gobot Gobot <firstname.lastname@example.org>
Reviewed-by: Robert Griesemer <email@example.com>
Kind of. We now have a SizesFor that supports returning different concrete Sizes implementations, but we don't exactly have a concrete implementation for cmd/compile--it's close, but not exact, e.g. the padding byte in some circumstances. Moving to unplanned, though, pending direct need for it.