Comment on Golang be like

CodeBlooded@programming.dev ⁨1⁩ ⁨year⁩ ago

• m_f@midwest.social ⁨1⁩ ⁨year⁩ ago

  That’s 👏 what 👏 CI 👏 is 👏 for

  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.

  source

  • 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
• Urik@lemmy.ca ⁨1⁩ ⁨year⁩ ago

  That’s a problem with your workplace, not the language.
  You could have a build setting for personal development where unused variables are not checked, and then a build setting for your CI system that will look for them. It gives you freedom to develop the way you want, but will not merge your PR unless the stricter rules are met.

  source

  • LittleLordLimerick@lemm.ee ⁨1⁩ ⁨year⁩ ago

    Why in the world would you want to develop something that doesn’t follow the coding rules required by your org, just so you can go back and fix everything before submitting a PR? That’s just extra work.

    source

    • planish@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

      Because you want to know if the first half of the code works at all before you write the whole second half.

      Finding all the bits that will be used by the second half and changing the declarations to just expressions is a bunch of extra work. As is adding placeholder code to use the declared variables.

      source

      • LittleLordLimerick@lemm.ee ⁨1⁩ ⁨year⁩ ago

        I’m having a hard time envisioning a situation where testing my code requires a bunch of unused variables. Just don’t declare the variables until you’ve started writing the code that uses them…

        source

        • -> View More Comments
  • CodeBlooded@programming.dev ⁨1⁩ ⁨year⁩ ago

    I concur, it is a problem with that workplace. (In this case, OP is just sharing a funny meme. I wouldn’t suggest this meme means they’re a problem. I could have made this meme and I love the feature.)

    Developing on a team at a company is like the “Wild West.” What’s considered to be acceptable will not only vary from workplace to workplace, but it can also fluctuate as developers and managers come and Go. Each of them have their own unique personality with their own outlook on what “quality” code looks like. (And many of them do not care about code quality whatsoever. They just need to survive 1-2 years there, make management happy with speedy deliveries, and then they can move on to the next company with a 30% pay bump.)

    Having experienced working with developers who frequently filled with code base with unused code while having no control over who will leave or join as a contributor to the code base, I think features like this make for a more sane development experience when you’re developing with a team of seemingly random people that you never personally invited to contribute to the code base.

    will not merge your PR unless the stricter rules are met.

    This doesn’t fly when you work in big corporate and the boss doesn’t care about the code meeting stricter rules. “A working prototype? No it’s not- that’s an MVP! Deploy it to production now and move onto the next project!”

    source
• AeonFelis@lemmy.world ⁨1⁩ ⁨year⁩ ago

  That’s what warnings are for. The jokes about programmers ignoring warnings are outdated - we live in an age where CIs run linters and style checkers on pull requests, there is no reason for a CI to not automatically reject code that builds with warnings.

  source
• pixeltree@lemmy.world ⁨1⁩ ⁨year⁩ ago

  I mean, yeah that kind of stuff absolutely should not be in production. However, it’s easy to see how it could be annoying while testing something while working on it. It being annoying doesn’t make it a bad feature, just as finding it annoying doesn’t make you a problem imo.

  source

  • redcalcium@lemmy.institute ⁨1⁩ ⁨year⁩ ago

    It is VERY annoying when you’re hunting for a bug. For example, when you comment out a function call to debug an issue, the compiler might suddenly complains about unused variables, so you’ll need to comment them out as well. Repeat several times and you’ll start having an urge to smack the monitor.

    source
• thanks_shakey_snake@lemmy.ca ⁨1⁩ ⁨year⁩ ago

  Lol new copypasta unlocked 🔓

  source

  • CodeBlooded@programming.dev ⁨1⁩ ⁨year⁩ ago

    🫡

    source
• redcalcium@lemmy.institute ⁨1⁩ ⁨year⁩ ago

  It costs a lot of time reasoning about it during pull request and it costs a lot of time arguing with coworkers who swear that they’re going to need that code in there next week (they never need that code).

  You should go to your team leader and ask them to enforce a coding standard. I agree with other commenters that said this should be a warning instead of an error.

  source
• fibojoly@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

  I was working for a team that did quality control on the code of an entire financial group and it’s still amazing to me the shit we let through.
  I feel annoyed even having compiler warnings in my code and here we were downgrading errors into warnings so the code would go through, or adding rules exceptions for a program so the team responsible could push a hotfix to prod… It’s all shit. All the way down.

  I dream of working with such a strict language.

  source
• ricojo777@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago

  I’ll start calling SQL “squeal” now in the spirit of this comment

  source

  • Magnetar@feddit.de ⁨1⁩ ⁨year⁩ ago

    No amount of propaganda will ever get me to pronounce it “sequel”. I’ll die in that hill.

    source

    • CodeBlooded@programming.dev ⁨1⁩ ⁨year⁩ ago

      Wait… how do you say it? es queue el?

      source

      • Magnetar@feddit.de ⁨1⁩ ⁨year⁩ ago

        I do, unashamedly.

        source