this post was submitted on 14 Feb 2024
534 points (96.7% liked)
Programmer Humor
24670 readers
103 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
Making a variable just to hold a debug value to look at with a breakpoint, but Go says no.
You can do
_ = variablePrint-style debugging/logging has entered the chat.
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.
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?
Its an effort to keep large code bases clean. I think they should allow them when running
go runbut not when building.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
Automated tests and version control should prevent that from being a problem, I imagine.
I totally agree that it’s really annoying when debugging, but
go runliterally 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.Has Google never heard of CI to perform such checks?
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.
Keep in mind that this is the same language that prefers function names ToBeLikeThis(), and the reason is that it looks different than Java.
Every time I think "perhaps I should give Golang another try", it's shit like this that keeps me noping out
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.
just dogsled shit