Alan Donovan a00bb74625 go/analysis/cmd/vet-lite: make CLI closer to cmd/vet ... Details: - Add -source, -v, and -all flags to vet-lite. These have no effect and issue a warning. - Add usage message to vet-lite that lists all analyzers and explains -foo.enable and other flags. - Factor this help message (common to vet-lite and multichecker) into analysisflags. - Add legacy aliases of new flags. e.g. -printfuncs is now -printf.funcs The old names work but issue a warning when used. Also: update comments to say -vettool not$GOVETTOOL I think we should probably do away with singlechecker in a follow-up: a singleton multichecker is good enough, and will allow us to remove cases in the flag-processing logic. Change-Id: Ib62f16b5e2f4c382a29e6300a6246b2db9e08049 Reviewed-on: https://go-review.googlesource.com/c/148559 Reviewed-by: Michael Matloob <matloob@golang.org>		2018-11-09 19:31:51 +00:00
..
analysistest	go/analysis/cmd/analyze: install all analyzers	2018-10-19 17:03:54 +00:00
cmd	go/analysis/cmd/vet-lite: make CLI closer to cmd/vet	2018-11-09 19:31:51 +00:00
internal	go/analysis/cmd/vet-lite: make CLI closer to cmd/vet	2018-11-09 19:31:51 +00:00
multichecker	go/analysis/cmd/vet-lite: make CLI closer to cmd/vet	2018-11-09 19:31:51 +00:00
passes	cmd/vet: lostcancel: suppress the check in the main.main function	2018-11-09 18:25:37 +00:00
singlechecker	go/analysis/internal/analysisflags: common flag handling	2018-10-19 17:43:12 +00:00
analysis.go	go/analysis: write package documentation	2018-10-08 17:31:26 +00:00
doc.go	go/analysis/cmd/vet: new name for cmd/analyze	2018-10-19 18:46:07 +00:00
validate.go	go/analysis: validate: report duplicates among analyzers (roots)	2018-10-11 19:55:00 +00:00