D105819 Added NoOwnershipChangeVisitor, but it is only registered when an off-by-default, hidden checker option was enabled. The reason behind this was that it grossly overestimated the set of functions that really needed a note:
std::string getTrainName(const Train *T) { return T->name; } // note: Retuning without changing the ownership of or deallocating memory // Umm... I mean duh? Nor would I expect this function to do anything like that... void foo() { Train *T = new Train("Land Plane"); print(getTrainName(T)); // note: calling getTrainName / returning from getTrainName } // warn: Memory leak
This patch adds a heuristic that guesses that any function that has an explicit operator delete call could have be responsible for deallocating the memory that ended up leaking. This is waaaay too conservative (see the TODOs in the new function), but it safer to err on the side of too little than too much, and would allow us to enable the option by default *now*, and add refinements one-by-one.
These serve to identify new/delete operators. I've done a lot of work to make this better, but I don't remember why isFreeingCall doesn't call these.