The compiler internal error (now circumvented) reported in #81241 is due to a missing (cmd/compile/internal/types) type Object (Type.obj) of a struct. With a nil obj field, the type position is unknown which lead to an internal compiler error in that case.
The Type.obj field should be set at some point, perhaps after TFORW types are resolved (which would still be too late for the above case). It's also not clear where a type's position should be stored in the type is unnamed; presumably no Object exists in that case.
A cursory investigation seemed to imply that Type.obj is mostly (always?) nil.
Should investigate and resolve as this may be the cause for possibly other internal compiler errors.
The compiler internal error (now circumvented) reported in #81241 is due to a missing (cmd/compile/internal/types) type
Object(Type.obj) of a struct. With a nilobjfield, the type position is unknown which lead to an internal compiler error in that case.The
Type.objfield should be set at some point, perhaps afterTFORWtypes are resolved (which would still be too late for the above case). It's also not clear where a type's position should be stored in the type is unnamed; presumably noObjectexists in that case.A cursory investigation seemed to imply that
Type.objis mostly (always?) nil.Should investigate and resolve as this may be the cause for possibly other internal compiler errors.