Comment on Give me Options or give me death

• Valmond@lemmy.mindoki.com ⁨11⁩ ⁨months⁩ ago

  Whoah, that seems like you’d flesh out code elsewhere, you know when you throw stuff together to make it work, and then fix it up to standards.

  Feels like you should have to make git commits perfectly well before being able to compile…

  Put that overwhelmingly intrusive thing in a hook checking out your commits instead (when you push your branch ofc).

  source

  • firelizzard@programming.dev ⁨11⁩ ⁨months⁩ ago

    You get used to it. The only time I really notice it these days is when I’m debugging and commenting out code.

    source

    • expr@programming.dev ⁨11⁩ ⁨months⁩ ago

      So… A lot of the time?

      source

      • firelizzard@programming.dev ⁨11⁩ ⁨months⁩ ago

        *when I’m doing debugging that requires commenting out code.

        Most of the time, I don’t comment out code. I run the code in a debugger, step through it, and see how the behavior deviates from what I expect. I mostly only resort to commenting out code if I’m having trouble figuring out where the problem is coming from, which isn’t that often.

        source
      • Valmond@lemmy.mindoki.com ⁨11⁩ ⁨months⁩ ago

        “Nah, only when working…”

        source
• TheSambassador@lemmy.world ⁨11⁩ ⁨months⁩ ago

  What reason is there for this when the compiler could just optimize that variable out of existence? This feels like the most hand holdy annoying “feature” unless I’m missing something.

  source

  • frezik@midwest.social ⁨11⁩ ⁨months⁩ ago

    Cleaner code. That’s all.

    If you need to take variable for some reason (like it’s a function that has to follow an interface, but it doesn’t need a specific parameter in this case), then you can prefix it with an underscore.

    source

    • expr@programming.dev ⁨11⁩ ⁨months⁩ ago

      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.

      source

      • dbx12@programming.dev ⁨11⁩ ⁨months⁩ ago

        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”

        source

        • -> View More Comments
      • frezik@midwest.social ⁨11⁩ ⁨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.

        source