db798565ff
Alternative build systems like blaze don't always provide a way to determine the relationship between a package and the package it's testing. This means that sometimes the check for misspelled Example function names over-reports because it doesn't find the object being exemplified. Don't report errors unless a object can't be found in any of the imports. This means that there won't be any false positives though of course this comes at the cost of false positives. Change-Id: I7435eeb2333b6dd72e06bb6383fff2ac17bee845 Reviewed-on: https://go-review.googlesource.com/c/tools/+/168404 Run-TryBot: Michael Matloob <matloob@golang.org> Reviewed-by: Ian Cottrell <iancottrell@google.com> |
||
|---|---|---|
| .. | ||
| analysistest | ||
| cmd/vet | ||
| internal | ||
| multichecker | ||
| passes | ||
| singlechecker | ||
| unitchecker | ||
| analysis.go | ||
| doc.go | ||
| validate.go | ||