On 05/12/2017 05:16, Alec Thomas wrote:
Hello,
Through the efforts of many contributors, and in particular those of
Daniel Nephin, v2.0.0 has been released. You can grab it here:
https://github.com/alecthomas/gometalinter/releases/tag/v2.0.0
The biggest change since v1.x is that linting is now MUCH more
efficient, thanks to the changes by Daniel. Instead of invoking each
linter for every directory, linters are invoked the minimum number of
times necessary by passing as many directories, packages or files as
they will accept in a single invocation.
The configuration format has also changed, but should be mostly
backwards compatible.
Another major change is that from now on we will be releasing binary
packages. This also means that: gometalinter's management of linter
installation will soon be deprecated, and eventually removed, and that
gopkg.in will no longer be used.
Going forward we have several interesting things planned for gometalinter:
1. Support for in-process invocation of linters via an interface +
adapters. See https://github.com/alecthomas/gometalinter/issues/380.
This should make linting even more efficient, as packages will only
need to be parsed/compiled once, and the FileSet (etc.) can be reused.
2. Configuration handling will be rewritten/rethought. This will
encompass automatic .gometalinterrc loading, among other things.
This is great news Alex, thanks for everyone's hard work #2
(.gometalinterrc loading) is the killer feature for us.
Currently we have to invoke gometalinter for each package on the command
line separately, which prevents any benefits of v2. speedup.
3. Lots of internal refactoring to clean up the codebase.
As always, if you encounter any problems please create a new issue.
Regards
Steve
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
