-
Notifications
You must be signed in to change notification settings - Fork 8
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.
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
Should Writable require Semiregular, or "Move-Defaultable" #240
Labels
Comments
I think it was just an oversight. |
|
ericniebler
added a commit
that referenced
this issue
Nov 17, 2016
ericniebler
added a commit
that referenced
this issue
Jan 18, 2017
ericniebler
added a commit
that referenced
this issue
Feb 1, 2017
ericniebler
added a commit
that referenced
this issue
Feb 15, 2017
ericniebler
added a commit
that referenced
this issue
Feb 18, 2017
ericniebler
added a commit
that referenced
this issue
Feb 18, 2017
ericniebler
added a commit
that referenced
this issue
Feb 18, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
P0022R2 changes the
Readable
concept by replacing theSemiregular
requirement withMovable
andDefaultConstructible
; this allows move-only types likeunique_ptr<int>
andoptional<thread>
to modelReadable
.P0022R2 notably does not make the symmetric change to the
Writable
concept. Why should I be forbidden to write to these move-only types from which I may read?Note that this discrepancy is exacerbated by the fact that both implementations (cmcstl2, range-v3) of the TS have already implemented the same relaxation for
Writable
.EDIT:
Proposed Resolution
[Editorial note: Change the definition of
Writable
([iterators.writable]) as follows: --end note]The text was updated successfully, but these errors were encountered: