539

submitted 8 months ago* (last edited 5 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

[-] xmunk@sh.itjust.works 61 points 8 months ago

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.

[-] herrvogel@lemmy.world 8 points 8 months ago

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 8 months ago* (last edited 8 months ago)

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

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

load more comments (5 replies)

load more comments (8 replies)

load more comments (13 replies)

this post was submitted on 14 Feb 2024

539 points (96.7% liked)