This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of Resolved status.
Section: 16 [library] Status: Resolved Submitter: Switzerland Opened: 2010-08-25 Last modified: 2018-05-20
Priority: Not Prioritized
View other active issues in [library].
View all other issues in [library].
View all issues with Resolved status.
The general approach on moving is that a library object after moving out is in a "valid but unspecified state". But this is stated at the single object specifications, which is error prone (especially if the move operations are implicit) and unnecessary duplication.
[ Resolution proposed by ballot comment ]
Consider putting a general statement to the same effect into clause 17.
[2010-11-05 Beman provides exact wording. The wording was inspired by Dave Abrahams' message c++std-lib-28958, and refined with help from Alisdair, Daniel, and Howard. ]
[2011-02-25 P/R wording superseded by N3241. ]
Resolved by N3241