Make linter facter by enabling bazel nogo to implement fast incremental linter

[hawkingrei]

Enhancement

nogo build-time code analysis

nogo is a tool that analyzes the source code of Go programs. It runs alongside the Go compiler in the Bazel Go rules and rejects programs that contain disallowed coding patterns. In addition, nogo may report compiler-like errors.

nogo is a powerful tool for preventing bugs and code anti-patterns early in the development process. It may be used to run the same analyses as vet, and you can write new analyses for your own code base.

• vet
• staticcheck
• prealloc
• *: enable durationcheck for nogo linter #35661
• *: enable ineffassign #35670
• *: enable exportloopref  #35680
• *: enable gofmt #35721
• *: enable errcheck for nogo #35704
• *: enable all gosimples #35762
• *: enable unconvert #35821
• *: enable gci #35823
• *: support predeclared and asciicheck #35895
• *: enable gci #35823
• *: enable misspell #35719
• *: enable gosec #35873
• *: enable revive #35970
• *: enable bodyclose #36927

[tisonkun]

Could you add a link to nogo and try to prepare a table comparing nogo and govet, pros and cons?

[hawkingrei]

Could you add a link to nogo and try to prepare a table comparing nogo and govet, pros and cons?

This document is about nogo

[hawkingrei]

Could you add a link to nogo and try to prepare a table comparing nogo and govet, pros and cons?

I think the advantage of nogo is that it has a good mechanism to get cache results and share the cache anywhere. the disadvantage of it is that it makes a person manage the linter by code. here is an example from cockroach. and this is a library to do it.

[hawkingrei]

BTW, I have a plan to use Bazel nogo and golang.Ast to check the problem that RecordSet is not closed in the test like #35373.

[hawkingrei]

We have removed golangci-linter in the CI. The performance of the linter has sped up 10x. We can close this issue.