Comment on Give me Options or give me death

• 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

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

        I can see the sentiment here… Going through 100 clippy warning on Rust is just not fun… I know there’s the good old clippy --fix but I’m paranoid it breaks my code accidentally.

        Could probably have a compromise like 5 unused variables and your code don’t compile

        source

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

        Or, you know, treat it as a warning like literally every other language. There’s absolutely no good reason for it to prevent a build outright, but then again, there’s not really good reasons for many of the decisions behind go.

        source
      • nutomic@lemmy.ml ⁨4⁩ ⁨months⁩ ago

        Has Google never heard of CI?

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

        I totally agree that it’s really annoying when debugging, but go run literally builds then executes. I think what they should do is add a build flag. So debug builds can pass that flag to get the builder to shut up, and leave it enabled for production builds.

        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

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

        Every time I think “perhaps I should give Golang another try”, it’s shit like this that keeps me noping out

        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

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

        So… A lot of the time?

        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

      • expr@programming.dev ⁨4⁩ ⁨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

        • -> 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