On Sun, Dec 11, 2022, 2:03 AM Marcello H <marcel...@gmail.com> wrote:
> Ok, but does my answer really matter? Because in the end it's what any > linter will tell us about the software. > And since it is not hard to do, my suggestion always is to make use of > some of the great linters that exist. > > In a new project I always start off with all the linters (in > golangci_lint) active, and then deactivate the ones that I don't want. > You can also do it the other way around, just a matter of "how to begin > with linting". > The advantage of using some linter would be that it is also a kind of > quality fixation on the code. > Perhaps deciding on which linter(s) to use at first and then slowly > "inject" more. > > This post is not about finger-pointing btw, because if needed, I would > offer my help with this. > But I won't touch the functions with the high cognitive complexity ;-) > We do use a linter on the Go standard library: go vet. When some change in go vet causes it to report errors in existing code, we fix them. Ian > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcWYFQQTdknAv2dqnvpQCxqXo8Nr2NcT3W9-Q3zO4PswKA%40mail.gmail.com.
