Programmer Humor

19623 readers

112 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

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 1 year ago

MODERATORS

[email protected]

527

??? (lemm.ee)

submitted 9 months ago* (last edited 6 months ago) by [email protected] to c/[email protected]

67 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 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 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

[–] [email protected] 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.

[–] [email protected] 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.

[–] [email protected] 2 points 9 months ago* (last edited 9 months ago)

Has Google never heard of CI to perform such checks?

[–] [email protected] 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.