-
Notifications
You must be signed in to change notification settings - Fork 193
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
Move to fieldalignment linter from deprecated maligned linter #1252
Comments
This is also reported as a warning in Go linting:
|
fieldalignment replaces maligned. This currently raises a number of linting errors because fieldalignment cares about pointer ordering (for GC); see golang/go#44877 for details. Fixes: submariner-io#1252 Signed-off-by: Stephen Kitt <[email protected]>
The switch itself is implemented in #1306, however it shows that Further, golangci-lint can use |
Okay, thanks for digging in and summarizing so clearly @skitt. Can we add golangci-lint ignores for this linter matching text "pointer size" (or similar) to turn
I don't see either So maybe the plan could be something like:
|
fieldalignment replaces maligned. Errors related to pointer ordering (for GC) are ignored; see golang/go#44877 for details. Fixes: submariner-io#1252 Signed-off-by: Stephen Kitt <[email protected]>
Ah yes, I’d forgotten we could do that! I’ve added the relevant configuration in the updated PR. If it passes everything here I’ll mark it as ready for review. |
fieldalignment replaces maligned. Errors related to pointer ordering (for GC) are ignored; see golang/go#44877 for details. Fixes: submariner-io#1252 Signed-off-by: Stephen Kitt <[email protected]>
fieldalignment replaces maligned. Errors related to pointer ordering (for GC) are ignored; see golang/go#44877 for details. Fixes: #1252 Signed-off-by: Stephen Kitt <[email protected]>
What would you like to be added:
Move from the deprecated maligned linter to the new fieldalignment linter.
Why is this needed:
Upgrading to golangci-lint 1.39.0 in submariner-io/shipyard#519:
The text was updated successfully, but these errors were encountered: