Programmer Humor

19564 readers

1005 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]

538

??? (lemm.ee)

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

75 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 (10 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?

[–] [email protected] 8 points 9 months ago* (last edited 9 months ago) (6 children)

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

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

load more comments (4 replies)

load more comments (7 replies)