-
Notifications
You must be signed in to change notification settings - Fork 17.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
go/types, types2: scope is unset on receivers of instantiated methods #51920
Comments
Change https://go.dev/cl/395538 mentions this issue: |
@gopherbot please consider this for backport to 1.18, it is an oversight. |
Backport issue(s) opened: #52007 (for 1.18). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases. |
Change https://go.dev/cl/395680 mentions this issue: |
…substituting receivers For #51920 Fixes #52007 Change-Id: I29e44a52dabee5c09e1761f9ec8fb2e8795f8901 Reviewed-on: https://go-review.googlesource.com/c/go/+/395538 Trust: Robert Findley <rfindley@google.com> Run-TryBot: Robert Findley <rfindley@google.com> Reviewed-by: Robert Griesemer <gri@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> (cherry picked from commit 9b90838) Reviewed-on: https://go-review.googlesource.com/c/go/+/395680
While prototyping #51682, I observed that while substituting in method receivers we do not set the parent scope.
This is unintended, and should probably be fixed for 1.18.1.
CC @griesemer
The text was updated successfully, but these errors were encountered: