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.

[–] AlexWIWA@lemmy.ml 15 points 9 months ago (2 children)

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

[–] pipe01@programming.dev 8 points 9 months ago

You can do _ = variable

[–] dejected_warp_core@lemmy.world 2 points 9 months ago* (last edited 9 months ago)

Print-style debugging/logging has entered the chat.

[–] technojamin@lemmy.world 13 points 9 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.

[–] herrvogel@lemmy.world 8 points 9 months ago (2 children)

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?

[–] YIj54yALOJxEsY20eU@lemm.ee 8 points 9 months ago* (last edited 9 months ago) (4 children)

Its an effort to keep large code bases clean. I think they should allow them when running go run but not when building.

[–] RustyNova@lemmy.world 5 points 9 months ago (1 children)

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 2 points 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.

[–] firelizzard@programming.dev 3 points 9 months ago* (last edited 9 months ago) (1 children)

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~~ those errors enabled for production builds.

[–] nutomic@lemmy.ml 2 points 9 months ago* (last edited 9 months ago)

Has Google never heard of CI to perform such checks?

[–] expr@programming.dev 1 points 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.

[–] frezik@midwest.social 5 points 9 months ago (1 children)

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

[–] fadhl3y@lemmy.world 4 points 9 months ago (1 children)

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

[–] YIj54yALOJxEsY20eU@lemm.ee 2 points 9 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.

[–] pkill@programming.dev 1 points 9 months ago

just dogsled shit