4 ms·
Either you have warnings, or you have no warnings. The problem with no warnings is not that the warnings were "fixed", but that they get disabled. That is far m
by devwastaken 5y ago
Either you have warnings, or you have no warnings. The problem with no warnings is not that the warnings were "fixed", but that they get disabled. That is far more problematic.
- krzyk 5y agoDisabled or just shown, doesn't matter they will proliferate unless turned into errors.
- daemin 5y agoIf they're disabled then they will proliferate even if they are turned into errors. Better to be visible and culled promptly than disabled in code and hidden away.
- krzyk 5y agoWhy would you disable them? You fix it and done. If you start your project with 0 warnings and enforce it in CI it is responsibility of developer who adds the code to make it warnings free and not disable the warning (that needs to be checked in code review).
- krzyk 5y agoWhy would you disable them? You fix it and done.