28
Is it a bad practice to replace compiler warnings with a bunch of TODO notes? (lemmy.zip)
submitted 5 months ago by to c/programming@programming.dev
11 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
[–] 44 points 5 months ago

It is bad practice. You'll obviously have 0 warnings if you hide the warnings. You don't go from warnings to YOLO mode. You should compile with "warnings as errors" and fix those if you want to really remove those warnings.

  • permalink
  • fedilink
  • source
    •