@@ -386,12 +386,13 @@ Thanks to developers and authors of used linters:
386
386
- [ dominikh/go-tools/megacheck] ( https://github.com/dominikh/go-tools/tree/master/cmd/megacheck )
387
387
388
388
# Future Plans
389
- 1 . Fully integrate all used linters: make common interface and reuse 100% of what can be reused: AST traversal, packages preparation etc.
390
- 2 . Make it easy to write own linter/checker: it should take minimum code, have perfect documentation, debugging and testing tooling.
391
- 3 . Speedup packages loading (dig into [ loader] ( golang.org/x/tools/go/loader ) ): on-disk cache and existing code profiling-optimizing.
392
- 4 . Analyze (don't only filter) only new code: analyze only changed files and dependencies, make incremental analysis, caches.
393
- 5 . Smart new issues detector: don't print existing issues on changed lines.
394
- 6 . Integration with Text Editors. On-the-fly code analysis for text editors: it should be super-fast.
395
- 7 . Minimize false-positives by fixing linters and improving testing tooling.
396
- 8 . Automatic issues fixing (code rewrite, refactoring) where it's possible.
397
- 9 . Documentation for every issue type.
389
+ 1 . Upstream all changes of forked linters.
390
+ 2 . Fully integrate all used linters: make common interface and reuse 100% of what can be reused: AST traversal, packages preparation etc.
391
+ 3 . Make it easy to write own linter/checker: it should take minimum code, have perfect documentation, debugging and testing tooling.
392
+ 4 . Speedup packages loading (dig into [ loader] ( golang.org/x/tools/go/loader ) ): on-disk cache and existing code profiling-optimizing.
393
+ 5 . Analyze (don't only filter) only new code: analyze only changed files and dependencies, make incremental analysis, caches.
394
+ 6 . Smart new issues detector: don't print existing issues on changed lines.
395
+ 7 . Integration with Text Editors. On-the-fly code analysis for text editors: it should be super-fast.
396
+ 8 . Minimize false-positives by fixing linters and improving testing tooling.
397
+ 9 . Automatic issues fixing (code rewrite, refactoring) where it's possible.
398
+ 10 . Documentation for every issue type.
0 commit comments