Coverity Prevent: how to handle “checked return” warning when I deliberately don't check the return?

Question

As the title suggest, for example, in 85% of the situation, I'd like to check the return code of foo(), but sometimes I really don't care about it, but this will raise Coverity warning.

What's the best way to deal with this problem? Changing Coverity settings doesn't count. :)

Answer 1

The correct way to suppress CHECKED_RETURN defect is to cast the return value you don't care about to a void. This has the additional advantage of making it clear to anyone reading the code that you don't care about return value, rather than that you forgot to check it.