-
Notifications
You must be signed in to change notification settings - Fork 18k
types2, go/types: type-checking expands type forever #48974
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
Comments
Hmm, why exactly is this package invalid? Looks ok to me, and a fix I'm working on for another recursive case makes this type-check without error. |
Premature conclusion. I've adjusted the title. |
Change https://golang.org/cl/356490 mentions this issue: |
Change https://golang.org/cl/356515 mentions this issue: |
@griesemer The issue is not fixed yet. i'm testing on
please reopen the issue |
The issue was closed when the change went in to go/types. It will be fixed in the compiler with the CL above. |
This is now fixed in the type-checkers, but the compiler still has an issue. Filed separate #49068 for that. |
This is from a comment in #48951, reported by @jkmpariab. Reproducer:
cc: @findleyr
The text was updated successfully, but these errors were encountered: