You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a constructor or assignment operator brought from a base class into a derived class has the signature of a copy/move constructor or assignment operator for the derived class ([class.copy.ctor], [class.copy.assign]), the using-declaration does not by itself suppress the implicit declaration of the derived class member;
According to [defns.signature.member]
⟨class member function⟩ name, parameter-type-list, class of which the function is a member, cv-qualifiers (if any), ref-qualifier (if any), and trailing requires-clause (if any)
A member of a base class cannot have the signature of the member of a derived class since the classes of which they are members are not the same.
The text was updated successfully, but these errors were encountered:
xmh0511
changed the title
[namespace.udecl] p4 The member function of a base class cannot have the signature with the one of a derived class
[namespace.udecl] p4 The member function of a base class does not have the signature with the one of a derived class
May 4, 2022
xmh0511
changed the title
[namespace.udecl] p4 The member function of a base class does not have the signature with the one of a derived class
[namespace.udecl] p4 The member function of a base class cannot have the signature of the one of a derived class
May 4, 2022
[namespace.udecl] p4 says
According to [defns.signature.member]
A member of a base class cannot have the signature of the member of a derived class since the classes of which they are members are not the same.
The text was updated successfully, but these errors were encountered: