C++: Inherited virtual functions duplicated when `using Base::func`

[ZedThree]

Describe the bug

If a derived class has a using declaration to bring in overloads of a virtual function, the overridden functions from the base class still appear in the output. Here's a minimal example:

struct Base {
  /// Zero arg impl
  virtual int foo() { return 42; };
  /// One arg impl
  virtual int foo(int x) { return x; };
};

struct Derived : public Base {
  using Base::foo;
  /// One arg override
  int foo(int x) override { return x + 1; }
};

(source + doxyfile: mvce.tar.gz)

which generates:

I would expect the virtual int (int x) function to not appear here, because the override hides it.

Version

This happens with 1.10.0 on openSUSE Tumbleweed 20240103, but I also compiled 1.8.20 and 1.9.0 from source and found the same issue. I couldn't easily compile older versions.

[albert-github]

In the documentation of the Base class I see also something peculiar:

I.e. twice the that the function is reimplemented in Derived

It looks like that:

  using Base::foo;

is causing the problems, when I comment this line the result looks like what OP expects.

[ZedThree]

Yes, sorry it is exactly the using declaration that causes the issue. Without this line the Base::foo() (zero-arg) overload is hidden by the Derived::foo(int) method, so this is required for valid code.

Removing that line generates:

which is what I expect.

EDIT: Strictly speaking, even this is not correct as without using Base::foo the int foo() method will be hidden by the int foo(int) overload, so arguably shouldn't be in the "inherited from Base" list

[doxygen]

@ZedThree Please verify if the referenced commit fixes the problem for you. Do not close the issue, this will be done automatically when the next official release becomes available.

[ZedThree]

@doxygen Thanks, this fixes it for me!

[doxygen]

This issue was previously marked 'fixed but not released',
which means it should be fixed in doxygen version 1.11.0.
Please verify if this is indeed the case. Reopen the
issue if you think it is not fixed and please include any additional information
that you think can be relevant (preferably in the form of a self-contained example).