A project I’ve been working on had 400+ compiler warnings and no one on the team seems to mind. In fact, many use the accumulation of warnings as a pseudo-progress indicator for a build: “Hey. The build is up to 350 warnings, it should be done any time now.”
This situation is way more common than you might think. Or maybe you’re used to it. I’ve always shared the opinion that compiler warnings are our friends. They help identify potential new problems early in development when those problems are easier to fix.
I understand that fixing compiler warnings across a large project can be difficult, but ignoring them can be risky. Risk is something I’d rather minimize, even if it means finishing a mundane task like fixing a compiler warning.
So yeah, I care about the message:
Local declaration of 'size' hides instance variable
You should too.