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.

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

US 2 (006): 2.1.1: Update ranged-for-loop wording #345

Closed
CaseyCarter opened this issue Feb 28, 2017 · 5 comments
Closed

US 2 (006): 2.1.1: Update ranged-for-loop wording #345

CaseyCarter opened this issue Feb 28, 2017 · 5 comments

Comments

@CaseyCarter
Copy link
Collaborator

CaseyCarter commented Feb 28, 2017

Editorial Comment

The wording no longer matches the more thoroughly reviewed form in the C++17 Working Draft.

Proposed Change

Entirely replace this wording with the proposed wording for C++17.

@ericniebler
Copy link
Owner

ericniebler commented Mar 1, 2017

2017-02-28 LEWG triage: LWG. (LEWG says yes, do it.)

@CaseyCarter CaseyCarter changed the title US 6: Update ranged-for-loop wording US 2 (006): 2.1.1: Update ranged-for-loop wording Mar 1, 2017
@CaseyCarter
Copy link
Collaborator Author

Our base document is C++14. I think before we can do this we need to determine - possibly with advisement from CWG - if both versions of the wording are normatively equivalent. I certainly do NOT want to require implementations of C++14 + Ranges to implement any other normative differences to range-based-for other than the relaxation to enable sentinel delimited ranges.

@CaseyCarter
Copy link
Collaborator Author

CaseyCarter commented Apr 10, 2017

CWG (in telecon) sensibly requests full text of the proposed change to the TS wording.

EDIT: Casey volunteers to provide that wording.

@CaseyCarter
Copy link
Collaborator Author

CWG in telecon approves the wording of the proposed change and is calling it tentatively ready. I am to get a P-number and submit it in the pre-meeting mailing to be moved in Toronto.

@ericniebler
Copy link
Owner

Awesome, thanks Casey!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants