-
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: missing return value for undefined type mentions <T>
#58742
Comments
CC @griesemer |
Seems to be a regression in new type checker, go1.17 only reports first error. |
Change https://go.dev/cl/471438 mentions this issue: |
Note that there are two separate, unrelated errors, and the compiler is correct to report both of them. I don't consider this a regression. (The 2nd error is not caused by the 1st one, i.e., it's not a follow-on error). The report is on the printing of |
@dominikh As mentioned above, I believe the compiler correctly reports two errors here, the issue is just the "spelling" of the Q: Do you have anything specific in mind about what else you'd like to see reported in this case? The I am inclined to not do anything here. Thoughts? |
If we can't do better, I think that at least |
Agreed.
That is unfortunate.
I primarily filed this issue because I vaguely remember that including Maybe to improve on Ian's suggestion we could even say |
Change https://go.dev/cl/473255 mentions this issue: |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What did you do?
What did you expect to see?
A compile error that doesn't mention
<T>
What did you see instead?
The text was updated successfully, but these errors were encountered: