We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm redoing the package file format and code, and that work should fix this.
Noticed while debugging a cmd/go issue:
$ echo package p >p.go $ echo 'import _ "./q"' >>p.go $ echo broken >q.a $ go tool compile p.go p.go:2: import /tmp/q.a: not a package file $
So far so good. But take the \n away from q.a:
$ echo -n broken >q.a $ go tool compile p.go compile: reading input: EOF $
That's not useful: it doesn't even say what file is broken.
Like I said, the new package file code should fix this. This issue is a reminder to verify that. Please don't send CLs fixing the old code.
The text was updated successfully, but these errors were encountered:
@rsc is this now fixed?
Sorry, something went wrong.
No, because the new packages haven't happened.
CL https://golang.org/cl/45950 mentions this issue.
eb86aba
No branches or pull requests
I'm redoing the package file format and code, and that work should fix this.
Noticed while debugging a cmd/go issue:
So far so good. But take the \n away from q.a:
That's not useful: it doesn't even say what file is broken.
Like I said, the new package file code should fix this. This issue is a reminder to verify that. Please don't send CLs fixing the old code.
The text was updated successfully, but these errors were encountered: