• YIj54yALOJxEsY20eU@lemm.eeOP
    link
    fedilink
    arrow-up
    0
    ·
    9 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.

    • RustyNova@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      9 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

      • Faresh@lemmy.ml
        link
        fedilink
        English
        arrow-up
        0
        ·
        9 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.

    • Ethan@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      ·
      9 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.

    • expr@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      9 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.