Hacker News Reader

You should use go vet

(There seems to be a documentation error.)

And try the race detector:

Though of course, it's hard to argue that it would be nice to prevent these from compiling.

Indeed, it's invaluable. I use "go vet" and have enabled all of the Gometalinter linters [1] that make sense.

"go vet" never warned me about goroutine closure errors, not sure why, maybe I was running an old version. But I'm glad that it's supported.

That said, some of the things that "go vet" catches should, in my opinion, be errors.

Well, that's an "easy" bug.

What about not-shadowing a "non-loop" variable?

Take a look at this question:

It's easy to mess up during refactoring, and there's pretty much no reason to allow it.