Warn in dev, enforce stuff like this in CI and block PRs that don't pass. Go is just being silly here, which is not surprising given that Rob Pike said

Syntax highlighting is juvenile. When I was a child, I was taught arithmetic using colored rods. I grew up and today I use monochromatic numerals.

The Go developers need to get over themselves.

[–] [email protected] 19 points 1 year 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.

func main() {  
    test := true  
}

Oops, golang doesn't like that.

func main() {  
    test := true  
    _ = test  
}

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.

[–] [email protected] 18 points 1 year ago (1 children)

reading my code after being up for 18 hours and having my eyes glaze over trying to parse the structure of my monochromatic code but then I remember Rob Pike said syntax highlighting is juvenile so I throw my head against that wall for another 3 hours

[–] [email protected] 18 points 1 year ago* (last edited 1 year ago)

Prescription glasses are juvenile. When I was a child, I was prescribed visual aid to help my nearsightedness. I grew up and today I raw-dog the road.

[–] [email protected] 7 points 1 year ago

I agree that golang is being dumb when you don't even have the option to tell it that this is a testing env or something. But the thing about syntax highlighting is not the same. One is about handholding the developer so much that it makes it even more difficult to develop, and the other is a completely optional feature that is so uselful and non intrusive that even wizardly editors like emacs use it.

[–] flumph 4 points 1 year ago (4 children)

What's a situation where you need an unused variable? I'm onboard with go and goland being a bit aggressive with this type of thing, but I can't think of the case where I need to be able to commit an unused variable.

[–] [email protected] 18 points 1 year ago

You probably wouldn't be committing this, unless you're backing up a heavily WIP branch. The issue is that if you're developing locally and need to make a temporary change, you might comment something out, which then requires commenting another now-unused variable, which then requires commenting out yet another variable, and so on. Go isn't helping you here, it's wasting your time for no good reason. Just emit a warning and allow CI to be configured to reject warnings.

[–] [email protected] 9 points 1 year ago

I will need it two minutes tops. If I don't use it by then, I'll delete it, especially if it gives a warning like Rust does. But this? It just gets in the way.

[–] jormaig 8 points 1 year ago

Have you looked at the post? Use case: you are testing something or playing around and you want to try something. That's supper common

[–] [email protected] 1 points 1 year ago

I have a use case in Powershell: my company has a number of scripts that are minimally but importantly customized per-location, and I have an otherwise unused "SiteId" variable where I keep the location name for that specific script for a quick sanity check when I'm looking them over for any reason. Not necessary, but useful to me. Probably wouldn't do the same thing in a compiled program, but I can at least see where someone might want something similar.