-
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: invalid operation errors need to print expression #48472
Comments
Change https://golang.org/cl/350929 mentions this issue: |
For #48472 Change-Id: I5072ebcf53e03fb5515c51a2ad01f02d72b30719 Reviewed-on: https://go-review.googlesource.com/c/go/+/350929 Reviewed-by: Robert Griesemer <gri@golang.org> Trust: David Chase <drchase@google.com>
Is this fixed? |
This is in the process of being fixed. CLs are pending. |
Another test case, bad error message at current tip:
|
Just to be clear: this is on our radar but may not be fixed before the freeze due to higher-priority items that are not just bug fixes. We will spend time on this during the freeze as needed because improving error messages is unlikely to destabilize the release. |
Change https://golang.org/cl/357229 mentions this issue: |
The new type checker no longer echoes the expression involved in an invalid operation. It should. The exact expression makes it eaiser for people to get their bearings when reading the error.
(The fine-grained position information might provide similar precision, but it requires tool support or character counting for humans to use.)
/cc @griesemer @findleyr
The text was updated successfully, but these errors were encountered: