Comment on Golang be like

• merc@sh.itjust.works ⁨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.

  source
• WhyEssEff@hexbear.net ⁨1⁩ ⁨year⁩ ago

  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

  source
• flumph@programming.dev ⁨1⁩ ⁨year⁩ ago

  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.

  source

  • m_f@midwest.social ⁨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.

    source
  • hare_ware@pawb.social ⁨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.

    source
  • jormaig@programming.dev ⁨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

    source
  • ggppjj@lemmy.world ⁨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.

    source