You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Change https://go.dev/cl/398154 mentions this issue: [release-branch.go1.18] go/types, types2: fix overlap test for union termlist
cherrymui
changed the title
cmd/go: type set overlapping implementation for interface types might be not correct [1.18 backport]
go/types, cmd/compile: type set overlapping implementation for interface types might be not correct [1.18 backport]
Apr 5, 2022
cherrymui
added
CherryPickApproved
Used during the release process for point releases
NeedsFix
The path to resolution is known, but the work has not been done.
and removed
CherryPickCandidate
Used during the release process for point releases
NeedsFix
The path to resolution is known, but the work has not been done.
labels
Apr 6, 2022
…termlist
Per the spec, "the type sets of all non-interface terms must be
pairwise disjoint (the pairwise intersection of the type sets must
be empty)" in a union.
For the overlap test, the existing implementation casually mixed
syntactic union terms (which may have interface type) with type set
terms (which are normalized/expanded and must not have interface
type). As a consequence, in some cases the overlap test failed.
This change skips terms with interface types in the overlap test.
For this cherry-pick, also rename the files ending in issue51607.go
to issue51607.go2 because the 1.18 branch requires tests containing
generic features to end in .go2.
Fixes#52119.
Change-Id: I8ae9953db31f0a0428389c6a45a6696aa2450219
Reviewed-on: https://go-review.googlesource.com/c/go/+/397695
Trust: Robert Griesemer <gri@golang.org>
Run-TryBot: Robert Griesemer <gri@golang.org>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Reviewed-by: Robert Findley <rfindley@google.com>
Reviewed-on: https://go-review.googlesource.com/c/go/+/398154
@griesemer requested issue #51607 to be considered for backport to the next 1.18 minor release.
The text was updated successfully, but these errors were encountered: