From a9de79b9c399bac5cdcd8714b935f00eab61c8b4 Mon Sep 17 00:00:00 2001
From: Easwar Swaminathan <easwars@google.com>
Date: Fri, 12 Apr 2019 10:08:23 -0700
Subject: [PATCH] Use 'go vet' and not 'go tool vet'. (#2768)

From [release notes](https://golang.org/doc/go1.12#vet):

The go vet command has been rewritten to serve as the
base for a range of different source code analysis tools. See
the golang.org/x/tools/go/analysis
package for details. A side-effect is that go tool vet
is no longer supported. External tools that use go tool vet must be
changed to use go vet. Using go vet instead of go tool vet should work
with all supported versions of Go.
---
 vet.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/vet.sh b/vet.sh
index 5b1f36be..2042133f 100755
--- a/vet.sh
+++ b/vet.sh
@@ -88,7 +88,7 @@ go list -f {{.Dir}} ./... | xargs go run test/go_vet/vet.go
 gofmt -s -d -l . 2>&1 | fail_on_output
 goimports -l . 2>&1 | fail_on_output
 golint ./... 2>&1 | (! grep -vE "(_mock|\.pb)\.go:")
-go tool vet -all .
+go vet -all .
 
 # - Check that generated proto files are up to date.
 if [[ -z "${VET_SKIP_PROTO}" ]]; then