Comment on Give me Options or give me death

bleistift2@feddit.de ⁨4⁩ ⁨months⁩ ago

• RustyNova@lemmy.world ⁨4⁩ ⁨months⁩ ago

  Not a go dev. Is it really preventing compilation or is it just some hardened linting rules? Most languages can prevent compile on those errors, but that seems bad if it’s not a warning

  source

  • xmunk@sh.itjust.works ⁨4⁩ ⁨months⁩ ago

    Yes, and it fucking sucks. It’s a great thing to lint for but it makes debugging such a pain - commenting out an irrelevant block to focus your debugging will sometimes break your ability to compile… it’s extremely jarring.

    source

    • AlexWIWA@lemmy.ml ⁨4⁩ ⁨months⁩ ago

      Making a variable just to hold a debug value to look at with a breakpoint, but Go says no.

      source

      • pipe01@programming.dev ⁨4⁩ ⁨months⁩ ago

        You can do _ = variable

        source
      • dejected_warp_core@lemmy.world ⁨4⁩ ⁨months⁩ ago

        Print-style debugging has entered the chat.

        source
    • technojamin@lemmy.world ⁨4⁩ ⁨months⁩ ago

      This is why many languages have errors and warnings as separate things. Errors for things that for sure prevent the program from working, and warnings for things that are probably wrong but don’t prevent things from working. If you have a setting to then treat warnings as errors (like for CI checks), then you get all the guarantees and none of the frustration.

      source
    • herrvogel@lemmy.world ⁨4⁩ ⁨months⁩ ago

      Have they given an explanation as to why that is? I mean why make it a fatal error that prevents compilation, when you could make it a warning and have the compiler simply skip it?

      source

      • YIj54yALOJxEsY20eU@lemm.ee ⁨4⁩ ⁨months⁩ ago

        Its an effort to keep large code bases clean. I think they should just differentiate between a debug build and production build. Maybe ensure the debug build can only only run if its in the same directory as the go.mod file.

        source

        • -> View More Comments
      • frezik@midwest.social ⁨4⁩ ⁨months⁩ ago

        Keep in mind that this is the same language that prefers function names ToBeLikeThis(), and the reason is that it looks different than Java.

        source

        • -> View More Comments
    • pkill@programming.dev ⁨4⁩ ⁨months⁩ ago

      just dogsled shit

      source
  • dbx12@programming.dev ⁨4⁩ ⁨months⁩ ago

    Unused variable is an error which fails to compile.

    source

    • Valmond@lemmy.mindoki.com ⁨4⁩ ⁨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 ⁨4⁩ ⁨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

        • -> View More Comments
    • TheSambassador@lemmy.world ⁨4⁩ ⁨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 ⁨4⁩ ⁨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

        • -> View More Comments
  • YIj54yALOJxEsY20eU@lemm.ee ⁨4⁩ ⁨months⁩ ago

    I don’t think its inherently bad but it feels jarring when the language allows you reference nill pointers. It’s so effective in its hand holding otherwise that blowing things up should not be so easy.

    source
  • GarytheSnail@programming.dev ⁨4⁩ ⁨months⁩ ago

    Yes but I’ve never found it to be that annoying.

    source