3 ms·
"too many warnings" is a very vague condition. For a similar example: The D compiler gives very few warnings and some people want to remove those as well. The
by qznc 11y ago
"too many warnings" is a very vague condition.
For a similar example: The D compiler gives very few warnings and some people want to remove those as well. The argument is that the compiler should not do the job of static analysis tools, just because it is convenient or easy. A compiler should either generate code or give an error.
If something is for developers only, make it debug-level.
However, in the server environment, there is also the IT/sysadmin role between user and developer. It makes sense to provide a level specifically for them. "warning" mostly fits that.
- mattmanser 11y agoA good example is when you're dealing with third party APIs. They break, a lot, without you really knowing why and often not really knowing how they're going to fall over (even google's, one of our reports using the Adwords API fell over last week because it was returning 500s for an hour or so and then just worked again). So say you're doing an hourly sync, and it falls over, you want to log a warning. It happens, no need to send out the fire engines. If you're getting a warning every hour, that's "too many warnings".