ennemi [he/him]

You can, if you want, opt into warnings causing your build to fail. This is commonly done in larger projects. If your merge request builds with warnings, it does not get merged.

In other words, it’s not a bad idea to want to flag unused variables and prevent them from ending up in source control. It’s a bad idea for the compiler to also pretend it’s a linter, and for this behaviour to be forced on, which ironically breaks the Unix philosophy principle of doing one thing and doing it well.

Mind you, this is an extremely minor pain point, but frankly this is like most Go design choices wherein the idea isn’t bad, but there exists a much better way to solve the problem.

If only there was some way the compiler could detect unused variable declarations, and may be emit some sort of “warning”, which would be sort of like an “error”, but wouldn’t cause the build to fail, and could be treated as an error in CI pipelines

I never liked the idea some people have that Wal Mart and Amazon prove anything about central economic planning. For one, they’re market actors ultimately, and their goals have nothing to do with fulfilling people’s material needs and everything to do with consuming the universe in order to make numbers go up. No matter how big they are they’re still just capitalist extraction devices.

Secondly, the Soviet Union already proved that planned economies work. That’s like THE thing they did the best. The McCarthyist conditioning runs so deep that even leftists can`t point at the most obvious example of what we want to accomplish.