go/golangci_lint.vim: set package linting to 1 #4602
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The present default of 0 causes excessive and unnecessary typecheck errors in all but the most trivial (single-file) packages. The standard Go unit of code is a directory, not a file, and optimizing for processing a single file provides negligible savings in processing time for a typical project, yet creates a lot of noise for the user.
w0rp
requested changes
Sep 5, 2023
|
This pull request has been automatically marked as stale because it has not been updated recently. Make sure to write tests and document your changes. See |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The present default of 0 causes excessive and unnecessary typecheck errors in all but the most trivial (single-file) packages. The standard Go unit of code is a directory, not a file, and optimizing for processing a single file provides negligible savings in processing time for a typical project, yet creates a lot of noise for the user.
Since those users that will specifically want single-file processing are less common, it's arguably reasonable for them to configure this back to zero in their vimrc.