#48765 PR contains an experimental implementation of this functionality.

Note that #48532 is probably going to need a similar (but probably more invasive) fix.

What do you mean by "eface type structures"?

Currently a value of empty interface type is a pair of pointers. The first pointer points to the runtime._type structure that describes the type stored in the interface. This is the same as the underlying structure held in a reflect.Type interface value returned by reflect.TypeOf.

Those type structures can already be identified in an executable by looking for the runtime.types symbol (up to the runtime.etypes symbol).

Do you need something more than that? If so, what?

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

What do you mean by "eface type structures"?

Currently a value of empty interface type is a pair of pointers. The first pointer points to the runtime._type structure that describes the type stored in the interface. This is the same as the underlying structure held in a reflect.Type interface value returned by reflect.TypeOf.

Those type structures can already be identified in an executable by looking for the runtime.types symbol (up to the runtime.etypes symbol).

Do you need something more than that? If so, what?

Thank you for your reply! I looked closely at the cmd/link part and found out that every type is placed inside runtime.types. Indeed, all the types stored in runtime2.eface structure can be found there.

This proposal has been declined as retracted.
— rsc for the proposal review group