-
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
US 2 (006): 2.1.1: Update ranged-for-loop wording #345
Comments
2017-02-28 LEWG triage: LWG. (LEWG says yes, do it.) |
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. |
CWG (in telecon) sensibly requests full text of the proposed change to the TS wording. EDIT: Casey volunteers to provide that wording. |
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. |
Awesome, thanks Casey! |
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.
The text was updated successfully, but these errors were encountered: