-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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.
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
avoid halting, instead check compilation errors #1172
Closed
alvarolm opened this issue
Jun 1, 2020
· 2 comments
· May be fixed by mansong1/golangci-lint#30, oat-eknarin-hugeman/golangci-lint#8, irinazheltisheva/golangci-lint#25, geraldywy/golangci-lint#6 or irinazheltisheva/golangci-lint#41
Closed
avoid halting, instead check compilation errors #1172
alvarolm opened this issue
Jun 1, 2020
· 2 comments
· May be fixed by mansong1/golangci-lint#30, oat-eknarin-hugeman/golangci-lint#8, irinazheltisheva/golangci-lint#25, geraldywy/golangci-lint#6 or irinazheltisheva/golangci-lint#41
Labels
Comments
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors. |
3 tasks
3 tasks
This was referenced Feb 2, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is your feature request related to a problem? Please describe.
i dont believe the linter should halt when compilation errors are detected, at least in those cases it could default to report those errors or run go tool compile
Describe the solution you'd like
run go tool compile when the linter halts as last measure
Describe alternatives you've considered
using another linter or metalinter
The text was updated successfully, but these errors were encountered: