Go1.18 Support

[lmittmann]

Many tools are not able to handle Go1.18 yet. Upgrading gofmt should be fairly easy, but golint or ineffassign could be problematic.

[peczenyj]

BTW
#378 (comment)

[spekary]

For reference, a project that make extensive use of 1.18 generics:

https://goreportcard.com/report/github.com/goradd/maps

gofmt chokes on it. golint, not too bad. Everything else is fine.

[phanirithvij]

Maybe switch or conditionally switch to staticcheck? golang/go#38968 (comment)

There's also golangci-lint which has support for many linters including staticcheck.

[shawnps]

Hello, GRC is now running on Go 1.18, and the golint check has been removed.

[spekary]

golint has been replaced with go vet, which is not nearly as robust as golint. The golint repo recommends Staticcheck as a replacement. Why not use that?

[shawnps]

@spekary just to clarify we were already running go vet, it didn't replace golint.

We can certainly take a look at running staticcheck.

[spekary]

Actually, a better system might be to use https://golangci-lint.run.

It might make go report card more flexible. It already includes running many of the checks here on go report card. It also makes it easy to turn particular linters on and off so that goreportcard can be more easily modified in the future.

Over at awesome-go we have been using goreportcard as one of the validations of code quality. However, now that goreportcard no longer uses go lint, its not as useful. Hopefully you guys can find another linter to work with?