Triviality of deleted special member functions
15.8 [class.copy]
Richard Smith

Created on 2014-05-15.00:00:00 last changed 57 months ago


Date: 2015-10-15.00:00:00

Rationale (October, 2015):

CWG feels that the triviality of a deleted function should be irrelevant. Any cases in which the triviality of a deleted function is observable should be amended to remove that dependency.

Date: 2015-11-10.00:00:00

Additional note, October, 2015:

Moved from "extension" status to "open" to allow consideration by CWG. See the additional discussion in issue 1734 for further details. See also issue 1496.

Date: 2014-11-24.00:00:00

Additional note, November, 2014:

See paper N4148.

Date: 2014-06-15.00:00:00

Notes from the June, 2014 meeting:

CWG felt that deleted functions should be trivial. See also issue 1590.

Date: 2014-11-24.00:00:00

The current wording of the Standard does not make clear whether a special member function that is defaulted and implicitly deleted is trivial. Triviality is visible in various ways that don't involve invoking the function, such as determining whether a type is trivially copyable and determining the result of various type traits. It also factors into some ABI specifications.

(See also issue 1734.)

Date User Action Args
2015-11-10 00:00:00adminsetmessages: + msg5983
2015-11-10 00:00:00adminsetmessages: + msg5982
2015-11-10 00:00:00adminsetstatus: extension -> nad
2015-05-25 00:00:00adminsetstatus: open -> extension
2014-11-24 00:00:00adminsetmessages: + msg5246
2014-07-07 00:00:00adminsetmessages: + msg5105
2014-05-15 00:00:00admincreate