> No, if you get warnings, it means that your code is (and was already) wrong. I get dozens of warnings for unused variables, signed unsigned conversions (wher

> No, if you get warnings, it means that your code is (and was already) wrong. I get dozens of warnings for unused variables, signed unsigned conversions (where the value range is API enforced), etc. . Long ago we had thousands of warnings and went through our code base just to get rid of them, I would be surprised if we fixed even one bug while doing that, most was just adding some verbose construct to be explicit about what was already happening. Warnings can be helpful, which is why I still have them enabled, but not everyone is.