Programming

25860 readers

240 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

Is it a bad practice to replace compiler warnings with a bunch of TODO notes? (lemmy.zip)

submitted 15 hours ago by SpiderUnderUrBed@lemmy.zip to c/programming@programming.dev

9 comments fedilink hide all child comments

I am using rust, but this applies to many other languages, I get warnings like, dead code, unused variables, and etc, and while I remove most of them, there are some im not sure of, I like running my program and there being 0 warnings, or 0 warnings as i scroll down my code, so for things im unsure of, i mark them so the compiler doesn't put warnings there. I also add comments, starting with TODO:, it has some information about what to think about when i revisit it, also the todo's gets highlighed in my IDE with my extension, but is this bad practice?

you are viewing a single comment's thread
view the rest of the comments

[–] BeigeAgenda@lemmy.ca 6 points 14 hours ago

I like to treat warnings as errors and refuse releases with errors.

Occasionally I disable single warning in a specific file because it does not make sense.

Using TODO also makes sense, I'm mostly used to seeing them years after when debugging.

In your case it sounds like you may end up ignoring all the TODO's as too many of them become noise. I would instead disable the specific warnings in the compilers options, instead of in the code, and then deal with the remaining.

Later you can disable one warning at a time and fix it.