cmd/vet: some change in behavior since Go 1.6 #14861
Comments
Does the This might be user error. The docs says:
You're passing files, but one is "package main" and one is "package version". |
No, it doesn't. But full file version is here.
Yes, I am. But these two files belong to single package by sense. There is the same situation in go. For example, package x509 and others. |
But in those cases, the go/build rules dictate how the files are selected, and the |
This may be related to #14754 . |
Thank you for help.
I understand, but then how does to do single separate package that contains its "native" source files ("package version") with executable source file(s) for go:generate mechanism ("package main" )? It seems naturally for me and I placed these files together in one package. In any case for go1.6 this way worked good (for me). |
I don't know what the right answer is here. I was just reading the code & docs for the first time. |
I have been facing this issue with go-dockerclient as well: https://travis-ci.org/fsouza/go-dockerclient/jobs/115602473#L326. It fails only on tip. |
@runningmaster , @fsouza , does the issue still exist after the #14754 is fixed? |
@valyala nope, it seems to be gone, thank you! |
Seems to be fixed. |
1 What version of Go are you using (
go version
)?2 What operating system and processor architecture are you using (
go env
)?3 What did you do?
I made mini test (note: dir govettest == $GOPATH):
Finally
4 What did you expect to see?
Silent output.
5 What did you see instead?
NOTE
go version go1.6 linux/amd64
gen.go
from package folderinternal/version
The text was updated successfully, but these errors were encountered: