1
0
mirror of https://github.com/golang/go synced 2024-11-12 13:00:57 -07:00
go/src/cmd/vet
Rob Pike b1fab09901 cmd/vet: fix a couple of minor word choices in README
No semantic change, just clarifying a bit by choosing better words
in a couple of places.

Change-Id: I4496062ee7909baf83d4d22d25e13ef93b358b4b
Reviewed-on: https://go-review.googlesource.com/55255
Reviewed-by: Ian Lance Taylor <iant@golang.org>
2017-08-14 04:15:59 +00:00
..
all cmd/vet/all: in case of vet panic, don't filter stacktrace 2017-06-29 23:22:38 +00:00
internal
testdata cmd/vet: check that C receivers are cgo imports 2017-08-09 02:23:51 +00:00
asmdecl.go
assign.go
atomic.go
bool.go
buildtag.go
cgo.go cmd/vet: check that C receivers are cgo imports 2017-08-09 02:23:51 +00:00
composite.go
copylock.go
dead.go
deadcode.go
doc.go
httpresponse.go
lostcancel.go
main.go cmd/vet: don't exit with failure on type checking error 2017-08-03 04:22:02 +00:00
method.go
nilfunc.go
print.go
rangeloop.go
README cmd/vet: fix a couple of minor word choices in README 2017-08-14 04:15:59 +00:00
shadow.go
shift.go
structtag.go
tests.go
types.go
unsafeptr.go
unused.go
vet_test.go cmd/vet: don't exit with failure on type checking error 2017-08-03 04:22:02 +00:00

Vet is a tool that checks correctness of Go programs. It runs a suite of tests,
each tailored to check for a particular class of errors. Examples include incorrect
Printf format verbs and malformed build tags.

Over time many checks have been added to vet's suite, but many more have been
rejected as not appropriate for the tool. The criteria applied when selecting which
checks to add are:

Correctness:

Vet's checks are about correctness, not style. A vet check must identify real or
potential bugs that could cause incorrect compilation or execution. A check that
only identifies stylistic points or alternative correct approaches to a situation
is not acceptable.

Frequency:

Vet is run every day by many programmers, often as part of every compilation or
submission. The cost in execution time is considerable, especially in aggregate,
so checks must be likely enough to find real problems that they are worth the
overhead of the added check. A new check that finds only a handful of problems
across all existing programs, even if the problem is significant, is not worth
adding to the suite everyone runs daily.

Precision:

Most of vet's checks are heuristic and can generate both false positives (flagging
correct programs) and false negatives (not flagging incorrect ones). The rate of
both these failures must be very small. A check that is too noisy will be ignored
by the programmer overwhelmed by the output; a check that misses too many of the
cases it's looking for will give a false sense of security. Neither is acceptable.
A vet check must be accurate enough that everything it reports is worth examining,
and complete enough to encourage real confidence.