Developers coming to Go from languages that use try/catch constructs, like Java or C#, may feel a bit turned around. The inner voice suggests using ′recover′ with ′defer′ as the nearest equivalent...
When switching from other languages the urge to reach for recover/defer as a try/catch substitute is real
This reads very much like an ad for their static code analyzer. There is no real advice, just examples for what their software caught. I wonder how many of these would also be caught by golangci-lint.
This reads very much like an ad for their static code analyzer. There is no real advice, just examples for what their software caught. I wonder how many of these would also be caught by golangci-lint.