This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of NAD status.
Section: 16.4.6.5 [member.functions] Status: NAD Submitter: Ville Voutilainen Opened: 2015-11-29 Last modified: 2018-11-12
Priority: 2
View all other issues in [member.functions].
View all issues with NAD status.
Discussion:
The combination of 16.4.6.5 [member.functions], paragraphs 2 and 3 that LWG 2259(i) does seems to drop a requirement that any call behaves as if no overloads were added. Paragraph 3 used to say "A call to a member function signature described in the C ++ standard library behaves as if the implementation declares no additional member function signatures." whereas the new wording says "provided that any call to the member function that would select an overload from the set of declarations described in this standard behaves as if that overload were selected."
This can be read as meaning that if there's no default constructor specified, like for instance forstd::ostream, an implementation is free to
add it. It can also be read as meaning that an implementation is free to
add any overloads that wouldn't change the overload resolution result
of any call expression that would select a specified overload. That's
vastly different from allowing extensions that add new functions rather
than new overloads.
Was this relaxation intentional?
[2016-04, Issues Telecon]
Ville provides a motivating example.
#include <iostream>
class my_stream : std::ostream
{
};
int main()
{
my_stream ms;
}
This example is accepted by libstdc++, msvc rejects it, and clang+libc++ segfault on melpon.org/wandbox o_O. An earlier clang+libc++ just accepts it. I don't think the implementation divergence is caused by the acceptance of the referred-to 2259(i), but it certainly seems to increasingly bless the implementation divergence.
[2016-05 Issues Telecon]
This is related to issue 2695(i).
[2018-08 Batavia Monday issue discussion]
Ville to provide wording.
[2018-08 Batavia Monday issue discussion]
Ville recommends NAD; because closing this would outlaw conforming extensions.
[2018-11 San Diego Thursday night issue processing]
Status to NAD
Proposed resolution: