Problem: When every linter claims it's fast, "fast" no longer has meaning:
$ golangci-lint linters|grep 'fast: true'|wc -l
68
$ golangci-lint linters|grep 'fast: false'
unused (megacheck): Checks Go code for ... [fast: false, auto-fix: false]
I don't want to pick on anyone's work, but many of the linters are in fact quite slow. I wouldn't use many of them with IDE on-save functionality, anyway.
A couple ideas:
- Get rid of the "fast" categorization and get rid of
--fast. This is probably not a good proposal.
- Use a quantitative metric to decide what is "fast." Not sure what this would look like or when/where it would be performed.
Thanks for the consideration.
Problem: When every linter claims it's fast, "fast" no longer has meaning:
I don't want to pick on anyone's work, but many of the linters are in fact quite slow. I wouldn't use many of them with IDE on-save functionality, anyway.
A couple ideas:
--fast. This is probably not a good proposal.Thanks for the consideration.