-
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
cmd/compile/internal/types2, go/types: don't panic when calling under/underlying #65344
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Comments
more minimal example: package main
type X Int
const Int = X(3)
func main () {
} |
cc @golang/compiler |
This seems to be problem in types2, since go1.17 and go.18 with
|
Change https://go.dev/cl/559335 mentions this issue: |
gopherbot
pushed a commit
that referenced
this issue
Feb 5, 2024
If we do know whether we need a type or not, make use of the information when we know that we don't have a type and bail out. Fixes the issue at hand and also improves some other error messages which now report that we don't have a type instead of reporting a cycle. For #65344. Change-Id: I11182efd452c485d89e6c09ead8a647ea05d7318 Reviewed-on: https://go-review.googlesource.com/c/go/+/559335 Run-TryBot: Robert Griesemer <gri@google.com> Auto-Submit: Robert Griesemer <gri@google.com> Reviewed-by: Robert Findley <rfindley@google.com> Reviewed-by: Robert Griesemer <gri@google.com> TryBot-Bypass: Robert Griesemer <gri@google.com> Reviewed-by: Cuong Manh Le <cuong.manhle.vn@gmail.com>
The specific issue at hand has been fixed with the above CL. |
ezz-no
pushed a commit
to ezz-no/go-ezzno
that referenced
this issue
Feb 18, 2024
If we do know whether we need a type or not, make use of the information when we know that we don't have a type and bail out. Fixes the issue at hand and also improves some other error messages which now report that we don't have a type instead of reporting a cycle. For golang#65344. Change-Id: I11182efd452c485d89e6c09ead8a647ea05d7318 Reviewed-on: https://go-review.googlesource.com/c/go/+/559335 Run-TryBot: Robert Griesemer <gri@google.com> Auto-Submit: Robert Griesemer <gri@google.com> Reviewed-by: Robert Findley <rfindley@google.com> Reviewed-by: Robert Griesemer <gri@google.com> TryBot-Bypass: Robert Griesemer <gri@google.com> Reviewed-by: Cuong Manh Le <cuong.manhle.vn@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
The following code snippet panics the compiler:
What did you expect to see?
Some errors reported
What did you see instead?
The text was updated successfully, but these errors were encountered: