duplInheritedMember false positive with mixed static and runtime functions

[Steve Albright]

static functions are confusing duplInheritedMember

warning: duplInheritedMember - The class 'TheClass' defines member function with name 'CreateLabel' also defined in its parent class 'TheParent'.

class TheParent
{
protected:
   static QObject* CreateLabel();
};

class TheClass : public TheParent
{
private:
      QObject* CreateLabel();
};

[CHR]

Having two functions with the same name can lead to mixups and confusion. Making one of them static doesn't prevent that.

[Steve Albright]

I don't totally disagree however you can have private functions with the same name and they don't conflict. Here we have functions that are intended to be called differently, one with a class, one without so it kind of seems like calling out the conflict isn't useful.

We only have this a few times in our very large code base, I have suppressed them but would rather not and would rather not rename either - the intent is the same and they are used differently.