That's what warnings are for and -werror for production builds in literally any other language. This has been a solved problem for a very long time.

[–] frezik@midwest.social 1 points 9 months ago

Sure. Tell that to the Go devs.

If the language weren't pushed by Google, nobody would pay it any attention. It's yet another attempt to "do C right" and it makes some odd choices in the attempt.

[–] dbx12@programming.dev 0 points 9 months ago (1 children)

I for my part prefer it that way. Makes sure the code stays clean and nobody can just silence the warnings and be done with it. Because why would you accept useless variables that clutter the code in production builds? Imagine coming back after some time and try to understand the code again. At least you have the guarantee the variable is used somehow and not just "hmm, what does this do? ..... ah, it's unused"

[–] expr@programming.dev 1 points 9 months ago (1 children)

...you don't accept them. Basically every programming language accepts some kind of -werror flag to turn warnings into errors. Warnings for development builds, errors for production builds. This has been a solved problem for a very long time. Not only is it assinine to force them to be errors always, it's semantically incorrect. Errors should be things that prevent the code from functioning in some capacity.

[–] dbx12@programming.dev 1 points 8 months ago (1 children)

Oh, that makes warnings errors and does not mean "ignore errors". I'm not too familiar with compiler flags. You could do some mental gymnastics to argue that the unused variable causes the compiler to exit and thus the code is not functioning and thus the unused variable is not a warning but an error :^)

[–] expr@programming.dev 1 points 8 months ago

It's a pretty standard flag in basically all compiled languages, just goes by a different name. -werror in C, -Werror in Java, TreatWarningsAsErrors in C#, etc.