Comment on Give me Options or give me death

• 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

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

        but I’m paranoid it breaks my code accidentally

        Automated tests and version control should prevent that from being a problem, I imagine.

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

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

        There’s two types of programming languages, the ones people complain about and the ones nobody uses. Go is still my most productive language and is killer for building webservers. I basically use it as a scripting language since it’s so fast to write, compile, and execute.

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

  just dogsled shit

  source