this post was submitted on 14 Feb 2024

539 points (96.7% liked)

Programmer Humor

19594 readers

530 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

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

539

??? (lemm.ee)

submitted 9 months ago* (last edited 6 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

[–] firelizzard@programming.dev 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.