go/types, types2: type parameters returned by the API should not have unresolved underlying #49788
Labels
FrozenDueToAge
NeedsFix
The path to resolution is known, but the work has not been done.
release-blocker
Milestone
With recent changes,
TypeParam.Underlying()
now potentially mutates the type parameter, as it lazily calculates the underlying constraint interface. This can lead to race conditions for unresolved type parameters returned from the API.As with other lazy types, we need to ensure that all type parameters creates by type checking or with the
go/types
API are fully resolved when they are returned to the caller.Relatively straightforward to fix, but needs to be a release blocker (pre-beta1).
CC @griesemer
The text was updated successfully, but these errors were encountered: