go/types, types2: stack overflow results after naming type parameter after interface name. #50517
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I wrote this package that names a type parameter the same as its interface and ran `go build .'
What did you expect to see?
It build or provide a helpful error about what I did wrong, especially something around
Thing
because it is undefined, but it seems Go flipped a switch before it noticed.What did you see instead?
This may possibly be related to or a duplicate of: #48619.
The text was updated successfully, but these errors were encountered: