danmar/cppcheck — comment on commit 772b8cc37de2e56998d352bceca57cdd7b9d568c
File:  line 0
By reif:

Here we go again. Why are you deliberately adding false negatives to hide a bug in cppcheck? Please don't keep doing this. The bug will never get fixed when it is hidden like this. There are hundreds of instances of bugs in cppcheck deliberately hidden like this that will NEVER get fixed because they are so well hidden. If you don't feel like fixing it, at least let other people know about it so it will hopefully get fixed. Fixing false positives should not be such a high priority that they are fixed immediately any way possible without any regard for the quality of cppcheck. Adding false negatives decreases the quality of cppcheck because you are diminishing it's ability to find real bugs in source code and that's the sole reason people use it in the first place. This is the only open source project I have ever worked on where the quality of the product produced was not a priority or even a concern.

Most bugs like this get hidden within minutes to hours of being found so there is no chance of them ever getting fixed before they are hidden away forever. Do we need a waiting period on false positives being fixed or a false negative impact study or a vote before false positives are fixed?