38981630ec
The analysistest.Run function now applies a single analysis to a set of packages, not just one, as this is necessary for testing the "tests" Analyzer. The Run function also returns a richer Result for each package, allowing a test to perform additional checks if necessary. I really don't understand how Gerrit decides whether to render a file such as passes/tests/tests.go as a mv+edit or an add; small changes to the CL seem to perturb the heuristic. When reviewing these CLs please inspect the logical diff of passes/vet/tests.go -> passes/tests/tests.go Change-Id: I7812837278b20c8608ccbb6c709c675588a84db1 Reviewed-on: https://go-review.googlesource.com/c/140457 Reviewed-by: Michael Matloob <matloob@golang.org> Run-TryBot: Michael Matloob <matloob@golang.org> |
||
|---|---|---|
| .. | ||
| asmdecl | ||
| assign | ||
| atomic | ||
| bools | ||
| buildtag | ||
| composite | ||
| copylock | ||
| ctrlflow | ||
| findcall | ||
| inspect | ||
| internal/analysisutil | ||
| loopclosure | ||
| lostcancel | ||
| nilfunc | ||
| pkgfact | ||
| stdmethods | ||
| tests | ||
| unreachable | ||
| unsafeptr | ||
| unusedresult | ||
| vet | ||
| README | ||
README
This directory does not contain a Go package, but acts as a container for various analyses that implement the golang.org/x/tools/go/analysis API and may be imported into an analysis tool. By convention, each package foo provides the analysis, and each command foo/cmd/foo provides a standalone driver.