this post was submitted on 14 Feb 2024
536 points (96.7% liked)

Programmer Humor

19315 readers
1 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
536
??? (lemm.ee)
submitted 7 months ago* (last edited 4 months ago) by YIj54yALOJxEsY20eU@lemm.ee to c/programmer_humor@programming.dev
75 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] YIj54yALOJxEsY20eU@lemm.ee 8 points 7 months ago* (last edited 7 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 7 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 7 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 7 months ago* (last edited 7 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 7 months ago* (last edited 7 months ago)

Has Google never heard of CI to perform such checks?

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