This page is a snapshot from the LWG issues list, see theLibrary Active Issues List for more information and the meaning ofResolved status.
noexcept move operationsSection: 16[library]Status:ResolvedSubmitter: BSIOpened: 2010-08-25Last modified: 2016-01-28
Priority:Not Prioritized
View otheractive issues in [library].
View all otherissues in [library].
View all issues withResolved status.
Discussion:
Addresses GB-61
All library types should have non-throwing moveconstructors and move-assignment operators unlesswrapping a type with a potentially throwing move operation.When such a type is a class-template, theseoperations should have a conditionalnoexceptspecification.
There are many other places where anoexceptspecification may be considered, but the move operationsare a special case that must be called out, to effectivelysupport themove_if_noexcept function template.
[Resolution proposed by ballot comment:]
Review every class and class template in the library. Ifnoexcept move constructor/assignment operators can be implicitly declared, then theyshould be implicitly declared, or explicitly defaulted. Otherwise, a move constructor/move assignment operator with anoexcept exceptionspecification should be provided.
[2010-10-31 Daniel comments:]
The proposed resolution ofn3157would satisfy this request.
[2011-03-24 Madrid meeting]
Resolved by papers to be listed later
Proposed resolution:
Seen3157