You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like x/tools/go/analysis is quickly becoming a new standard for writing static analysis in go. Being natively supported by tools like bazel's nogo it provides invaluable ability to unify all linters and perform static analysis at the build time.
errcheck being one of the most useful linters outside of go vet should greatly benefit from unification.
Are there any plans for doing this work or would you welcome contributions in this area?
The text was updated successfully, but these errors were encountered:
vitarb
changed the title
Migrating errcheck to use go/analysis
Migrating errcheck to go/analysis
May 1, 2019
There aren't any plans to rewrite the tool. Contributions are welcome, but I have to wonder if integrating this library would lead to a wholly different program?
The package now provides errcheck.Analyzer; see README for short description and API stability disclaimer. This makes errcheck go/analysis-compatible while keeping the existing CLI unchanged.
It looks like x/tools/go/analysis is quickly becoming a new standard for writing static analysis in go. Being natively supported by tools like bazel's nogo it provides invaluable ability to unify all linters and perform static analysis at the build time.
errcheck being one of the most useful linters outside of go vet should greatly benefit from unification.
Are there any plans for doing this work or would you welcome contributions in this area?
The text was updated successfully, but these errors were encountered: