-
Notifications
You must be signed in to change notification settings - Fork 18.1k
cmd/compile: improve error message in initialization loop #16503
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
Could we update the title of this bug from
to something maybe like
because fixers can't easily search for it. |
@davecheney, @odeke-em, done. |
Wow, thanks @davecheney and @bradfitz!! |
FWIW: Not sure making this more verbose helps much. If you read the messages together it's pretty clear, w/o repetition. But I defer to the sentiment of the majority here. |
The current formatting is not a mistake. |
The issue isn't the formatting, it's the wording: it clearly doesn't make sense: "prog.go:7: x refers to prog.go:9: y refers to prog.go:7: x". If a cycle has two edges, it doesn't take three lines to describe it. |
@willfaught It does with the current formatting which is less verbose. There's no need to change it. |
Uh oh!
There was an error while loading. Please reload this page.
Please answer these questions before submitting your issue. Thanks!
go version
)?The current play.golang.org version.
go env
)?The current play.golang.org version.
See https://play.golang.org/p/ISPl1bA6OP:
This:
This:
The text was updated successfully, but these errors were encountered: