Relationship to go fix (after go 1.26)?

[camsteffen]

Golang is modernizing go fix in Go 1.26. This leaves me wondering...

Is golangci-lint a superset of go fix?

Is it recommended to replace go fix with golangci-lint, or use both?

What configuration of golangci-lint is needed in order to replace (enable all of the features of) go fix?

What configuration of golangci-lint is needed in order to not be redundant with go fix if I use both?

[ldez]

go fix will grab some rules of gopls modernize, those rules are already available inside golangci-lint: https://golangci-lint.run/docs/linters/configuration/#modernize

[camsteffen]

Okay, so I think the answer to my questions is...

Is golangci-lint a superset of go fix?

Yes, I think. But this seems to be incidentally true rather than a strong guarantee.

I'm not sure if there's any overlap outside of modernize. From the 1.26 announcement, it sounds like other functionality in go fix is obsolete, or at least replaceable by golangci-lint (assuming based on the amount of support behind golangci-lint).

Is it recommended to replace go fix with golangci-lint, or use both?

Just use golangci-lint. Although they probably won't conflict if you use go fix sometimes.

What configuration of golangci-lint is needed in order to replace (enable all of the features of) go fix?

Enable the modernize linter.

What configuration of golangci-lint is needed in order to not be redundant with go fix if I use both?

Disable the modernize linter.