Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
cmd/vet: some change in behavior since Go 1.6 #14861
1 What version of Go are you using (
2 What operating system and processor architecture are you using (
3 What did you do?
I made mini test (note: dir govettest == $GOPATH):
4 What did you expect to see?
5 What did you see instead?
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
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 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.