Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove gometalinter comparison #1731

Merged
merged 2 commits into from
Feb 13, 2021
Merged

Remove gometalinter comparison #1731

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8e42670
Remove comparison doc item
pkuca Feb 12, 2021
86eb924
Revise gometalinter mention in performance doc
pkuca Feb 12, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions docs/src/config/sidebar.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,6 @@
link: "/product/roadmap/"
- label: "Trusted By"
link: "/product/trusted-by/"
- label: "Comparison"
link: "/product/comparison/"
- label: "GitHub"
link: "https://github.com/golangci/golangci-lint"
- label: Contributing
Expand Down
78 changes: 0 additions & 78 deletions docs/src/docs/product/comparison.mdx
View file
Open in desktop

This file was deleted.

5 changes: 3 additions & 2 deletions docs/src/docs/usage/performance.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,9 @@ Less `GOGC` values trigger garbage collection more frequently and golangci-lint
## Why `golangci-lint` is so fast

1. Work sharing
The key difference with gometalinter is that golangci-lint shares work between specific linters (golint, govet, ...).
We don't fork to call specific linter but use its API.

During operation, `golangci-lint` shares work between specific linters (like `golint`, `govet`, etc.).
We don't fork to call a specific linter, but instead use its API.
For small and medium projects 50-90% of work between linters can be reused.

- load `[]*packages.Package` by `go/packages` once
Expand Down