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
Another test case for handling of cycle detection: https://play.golang.org/p/DAftfsYBsrX is accepted and appears to run correctly. The similar (and functionally identical) program https://play.golang.org/p/AChHOplAHzp is not accepted with an incorrect type alias cycle error. And the simplified version eliminating the type name T https://play.golang.org/p/ozYsLzyDax8 is not accepted with a type checking loop error.
Yet all of them are functionally the same. Either all of them should be accepted or none of them should be accepted.
The text was updated successfully, but these errors were encountered:
For reference: gccgo accepts and runs the first two versions. It crashes with the 3rd version (issue #25679).
some related? #23823
@go101 Related in the sense that there are cycles. But there may be different code paths executed.
griesemer
Successfully merging a pull request may close this issue.
Another test case for handling of cycle detection:
https://play.golang.org/p/DAftfsYBsrX
is accepted and appears to run correctly. The similar (and functionally identical) program
https://play.golang.org/p/AChHOplAHzp
is not accepted with an incorrect type alias cycle error. And the simplified version eliminating the type name T
https://play.golang.org/p/ozYsLzyDax8
is not accepted with a type checking loop error.
Yet all of them are functionally the same. Either all of them should be accepted or none of them should be accepted.
The text was updated successfully, but these errors were encountered: