Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

GB-5: [utility.exchange] missing MoveConstructible/MoveAssignable requirement #182

Closed
sdutoit opened this issue Sep 19, 2013 · 3 comments
Closed

GB-5: [utility.exchange] missing MoveConstructible/MoveAssignable requirement #182

sdutoit opened this issue Sep 19, 2013 · 3 comments
Labels
ballot-comment Response to an NB or ISO comment on a ballot
Milestone
C++14 CD NB Response

Comments

@sdutoit
Copy link
Contributor

sdutoit commented Sep 19, 2013

N3733 GB-5 says:

The wording describes example code including the call of a move constructor, but there is no requirement stated that T be move constructible.

It goes on to propose:

We would like to add a new Para 1 before existing paragraph:
Requires: Type T shall be MoveConstructible (Table 20) and MoveAssignable (Table 22).
However the MoveAssignable concept currently does not cover cases where the source and destination types may differ.
@sdutoit
Copy link
Contributor Author

sdutoit commented Sep 19, 2013

Note: it's an effects clause, not an example.

@sdutoit
Copy link
Contributor Author

sdutoit commented Sep 23, 2013

Not a defect. Because the draft specifies "Equivalent to:", the requirements are already implicitly specified.

See [structure.specifications]/4:

Whenever the Effects: element specifies that the semantics of some function F are Equivalent to some code sequence, then the various elements are interpreted as follows. [...] the semantics of the code sequence are determined by the Requires:, Effects:, Postconditions:, Returns:, Throws:, Complexity:, Remarks:, Error conditions:, and Notes: specified for the function invocations contained in the code sequence.

@sdutoit
Copy link
Contributor Author

sdutoit commented Sep 24, 2013

LWG is opening an issue for this.

@sdutoit sdutoit closed this as completed Sep 24, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ballot-comment Response to an NB or ISO comment on a ballot
Projects
None yet
Milestone
C++14 CD NB Response
Development

No branches or pull requests
1 participant
@sdutoit