Austin Clements

This proposal has been added to the [active column](https://go.dev/s/proposal-status#active) of the proposals project and will now be reviewed at the weekly proposal review meetings. — aclements for the proposal review...

In general this seems like a good thing to support, but we need a concrete proposal that people are generally agreed on.

> Similarly, add a new field FullSectionNumber, of type int32, to debug/pe.COFFSymbol. > Similarly, add a new field FullSectNum, of type int32, to debug/pe.COFFSymbolAuxFormat5. I arrived at the same conclusion...

> For bigobj, Microsoft document a limit of 4,294,967,296 (2^32-1). This sounds like it either needs to be a uint32 or a type with an even larger range, like int64....

The `int64` was a minor problem. But we never found a way to address [my concern](https://github.com/golang/go/issues/75659#issuecomment-3407270487) about changing `COFFSymbol` and `COFFSymbolAuxFormat5` given the unsafe casts between them and current disk-compatibility.