go/types, types2: missing error for conflicting method types due to incremental unification #50704
Labels
FrozenDueToAge
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
Milestone
The following code type-checks, but probably shouldn't.
(note that there is no instantiation of
C
that has different argument types form
andn
). The reason for this is that the MissingMethod API (used internally for interface assertions) unifies individual methods separately, not the entire method set.Discovered while looking into #50658.
CC @griesemer
The text was updated successfully, but these errors were encountered: