When we try to satisfy the checker bugprone-unused-return-value we sometimes see that we call functions that are unworthy of their return values being checked.
Such functions should be refactored first.
Also, when we need to document all the possible return values of a function, it feels strange to have only 1 possible return value.
This check looks for functions that always return 0.
The fix-it proposes to make such functions void and removes the expression from the return statement.
This checker is similar in spirit to libreoffice's should-return-bool and should-be-a-constant: