You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The field alignment linting has its uses, but the fieldalignment: struct with X pointer bytes could be Y (govet) linting errors are maddening. Unfortunately it doesn't appear that there is a way to disable just the pointer bytes linting error while keeping the fieldalignment: struct with X bytes could be Y (govet) one active.
For now, I'm opting to re-enable the deprecated maligned linter.
- Enable `maligned` linter
- Disable `fieldalignment` settings
- until the Go team offers more control over the types
of checks provided by the `fieldalignment` linter or
`golangci-lint` does so.
refs GH-244
refs atc0005/go-ci#302
The field alignment linting has its uses, but the
fieldalignment: struct with X pointer bytes could be Y (govet)
linting errors are maddening. Unfortunately it doesn't appear that there is a way to disable just the pointer bytes linting error while keeping thefieldalignment: struct with X bytes could be Y (govet)
one active.For now, I'm opting to re-enable the deprecated
maligned
linter.refs GH-203
refs atc0005/go-ci#302
The text was updated successfully, but these errors were encountered: