š»š¼šššššāShiiieeettt.......
sbvI feel like modern compilers would turn their nose up at that shit. āDead code? Ewww! No way Iām letting that into my syntax tree!ā
A lot of IDEs would probably throw a warning about unreachable code.
Pyroimplying that any developer actually reads warnings
voxelmost of my (rust) projects have zero warnings, unless Iām in the middle of working on a feature
First thing I do on my projects is enable warnings as errors and increase my warning levels when reasonable.
Unfortunately, the same canāt be said on the projects I work on at work. Drives me crazy that we get likes 300+ warnings whenever we run the app and that we canāt change it because "theyāre just warnings*.
Itās not that we want to ignore warnings. Itās just that most warnings take time to fix.
Thereās only so many hours in a day. And we have to accept technical debt in order to deliver, and then pay it off later.
My job does it well by doing a āspringā and āsummerā cleaning where we can turn out 100+ warnings into the single digits. Then busy season happens again and weāre back to 200+.
Itās not that we want to ignore warnings.
Speak for yourself, I promise you the team I work on actively ignores warnings and doesnāt even want to solve them as they pop-up. Being told you canāt compare doubles (because of precision loss) and ignoring it is on the developer and isnāt even that hard to fix. Most of our warnings come from shit like that.
Like, I get it. Itās probably not worth it to hunt down every āunused variableā warning (especially in an API where we used to have a variable for it and we donāt use it anymore and we donāt want to break the existing API so we just leave it there), but thereās things that are just trivial to fix when youāre working on code thatās right next to it.