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.
And now we hear stories about how easy it is to hack systems with built in LLM's and when you think about it, they are basically trained to be as helpful and forthcoming as possible, and then we give them the keys to the system!
Hook is on my 1990s top 10, I recently re-watched it, and it's still great, with good music and story. And it hit's a bit different watching it as a parent, put down that phone and play!
I'm sure there is a use-case for AI/Machine Learning in combating climate change, I am also sure that building 1000 mega polluting data-centers filled with LLM's is the opposite of fixing climate.
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.