fix: Remove gomnd from golangci linters #1210
Merged
+0
−3
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
This linter causes more harm than good, encouraging practices that actively obfuscate simple values whose meaning could be derived from context. Since it has no context-awareness, it flags everything from file modes, to obvious iteration counters as "magic numbers." This determination is fairly straightforward for a reviewer to make by hand, and it comes up relatively infrequently. The best course of action, until a better (probably LLM-based) magic number detector can be found.
timraymond
changed the title
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
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.
This linter causes more harm than good, encouraging practices that actively obfuscate simple values whose meaning could be derived from context. Since it has no context-awareness, it flags everything from file modes, to obvious iteration counters as "magic numbers." This determination is fairly straightforward for a reviewer to make by hand, and it comes up relatively infrequently. The best course of action, until a better (probably LLM-based) magic number detector can be found.