Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
cmd/vet: more clearly document go tool vet on a single file #23916
What did you do?
After upgrading from 1.9.4 to 1.10, I ran
I have simplified the code that gave me the original issue and uploaded it
What did you expect to see?
No output, and a successful exit code. This command succeeded on Go 1.9.4.
What did you see instead?
What's happening here is that
It looks like this change in behaviour was introduced in an effort to run
I'm not really sure what the best course of action is here. My thought is that
referenced this issue
Feb 19, 2018
I confirmed the behavior differs between
So I guess the breaking change already happened, and there is a workaround (
Can we commit to saying
I understand that this change of behavior of
Both accept files. The question is whether it's a requirement that they form a complete package or not.
This was referenced
Feb 20, 2018
It's not clear to me what to do here. I feel like there is documentation for how the tool works at https://golang.org/cmd/vet. It's true that vet changed from 1.9 to 1.10, and that was documented in the release notes. The question now is: what, if anything, needs to change in the cmd/vet and/or cmd/go docs? It would be very helpful if people who think that there should be a change could send in a CL. Thanks.