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
@@ -209,7 +209,7 @@ The `unused` isn't merged because it has high memory usage.
209
209
210
210
Linters execution starts in `runAnalyzers`. It's the most complex part of the `golangci-lint`.
211
211
We use custom [go/analysis](https://godoc.org/golang.org/x/tools/go/analysis) runner there. It runs as much as it can in parallel. It lazy-loads as much as it can
212
-
to reduce memory usage. Also, it set all heavyweight data to `nil` as becomes unneeded to save memory.
212
+
to reduce memory usage. Also, it sets all heavyweight data to `nil` as becomes unneeded to save memory.
213
213
214
214
We don't use existing [multichecker](https://godoc.org/golang.org/x/tools/go/analysis/multichecker) because
215
215
it doesn't use caching and doesn't have some important performance optimizations.
@@ -297,7 +297,7 @@ A processor can hide issues (`nolint`, `exclude`) or change issues (`path_shorte
0 commit comments