fasterthanlime OP , vor einem Monat

Anyway, I still think you probably shouldn't write go, but if you do, please run this on your code, in CI: https://golangci-lint.run

dysfun , vor einem Monat

@fasterthanlime yeah rust is great. i wrote this completely safe rust code that isn't even slightly scary https://gist.github.com/jjl/4c8ebf4bee2943a2b2d277741e13b787

fasterthanlime OP , vor einem Monat

@dysfun looks alright to me!!

creepy_owlet , vor einem Monat

@fasterthanlime just make sure you have a really beefy machine: my laptop with 16G of RAM triggers the oom killer when running this tool on a somewhat larger project.

rakoo , vor einem Monat

@fasterthanlime

I don't see it in the page: why is gofmt and go vet not enough ?

fasterthanlime OP , vor einem Monat

@rakoo Although some linters in that collection are noisy and opinionated, many of them find real world problems before runtime. Try them on your projects and see if it finds some bugs!

groxx , vor einem Monat (Bearbeitet vor einem Monat)

@fasterthanlime @rakoo to add to ^ this:
Because go vet is extremely conservative by default, and will continue to be so because "only for guaranteed flaws" is the modus operandi, and doesn't get very many checks even if you include the opt-in stuff.

golangci-lint is a collection of both go vet and the most popular linters by the rest of the ecosystem.