540

submitted 1 year ago* (last edited 1 year 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 1 year 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 1 year 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 1 year ago* (last edited 1 year ago)

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

[-] firelizzard@programming.dev 3 points 1 year ago* (last edited 1 year ago)

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.