Skip to content
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/internal/types2: bad error messages for bad import #42988

Closed
griesemer opened this issue Dec 4, 2020 · 1 comment
Closed

cmd/compile/internal/types2: bad error messages for bad import #42988

griesemer opened this issue Dec 4, 2020 · 1 comment
Milestone

Comments

@griesemer
Copy link
Contributor

package p
import 'a'

produces

x.go:2:8: could not import a (can't find import: "a")
x.go:2:8: "a" imported but not used

It should complain about a not being a string.

@griesemer griesemer added this to the Go1.17 milestone Dec 4, 2020
@griesemer griesemer self-assigned this Dec 4, 2020
@griesemer
Copy link
Contributor Author

This was fixed as part of https://golang.org/cl/278114.

@golang golang locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants