merc , 11 months ago

Yeah, insisting on things like a variable being used will result in people using work arounds. It won’t result in people not doing it.

Then, because people trust the language to police this rule, the work-arounds and debug code will get committed.

<span style="font-weight:bold;color:#a71d5d;">func </span><span style="font-weight:bold;color:#795da3;">main</span><span style="color:#323232;">() {  
</span><span style="color:#323232;">    test </span><span style="font-weight:bold;color:#a71d5d;">:= </span><span style="color:#0086b3;">true  
</span><span style="color:#323232;">}  
</span>

Oops, golang doesn’t like that.

<span style="color:#323232;">func main() {  
</span><span style="color:#323232;">    test := true  
</span><span style="color:#323232;">    _ = test  
</span><span style="color:#323232;">}
</span>

Perfectly cromulent code.

If they really wanted to avoid people having unused variables, they should have used a naming convention. Any variable not prefixed by “_” or “debug” or whatever has to be used, for example. Then block any code being checked in that still contains those markers.