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
P2164 views::enumerate #875
Comments
P2164R1 views::enumerate (Corentin Jabot) |
A short summary of the feedback form ML, closed on 14 Sep 2020:
|
P2164R2 views::enumerate (Corentin Jabot) |
This will probably get rolled into the upcoming "Plan for C++23 ranges" effort. We'll leave it separate for now, but it should be tagged for meeting review not mailing list review. |
P2164R3 views::enumerate (Corentin Jabot) |
2021-02-09 Library Evolution TeleconP2164R3: 2021-02-09 Library Evolution Telecon Minutes SummarySome discussion was around having const members, which inhibit assignment. The general feeling was not to have them. The larger discussion was around whether or not we want named fields at all vs. tuple. The arguments in favor of tuple is that otherwise there is a lot more that needs to be added (comparisons, cross conversions, etc.). The author was asked to come back with a revision containing a cost-benefit analysis of adding a new type with named fields for this. OutcomeBring a revision of P2164R3 (
|
P2164R4 views::enumerate (Corentin Jabot) |
Reviewed by SG9 at Kona2022 meeting (Full Minutes). PollsPOLL: We would prefer the tuple solution for “P2164: views::enumerate” (which is the safer way).
Attendance: 15 (on-site 11, online 4) # of Authors: 1 Author’s position: F Outcome: Strong consensus in favor POLL: We support applying the resolution of “FR#416: FR-014-021 26.6 (range.factories) Add views::enumerate (duplicate: US#525)”, and forward “P2164: views::enumerate” to C++23 with the proposed resolution.
Attendance: 15: 4 11 # of Authors: 1 Author’s position: SF Outcome: Consensus in favor A: Oppose to adding features by NB comments SummaryThe author has presented the paper. There was a design question - whether we want tuple (which was implemented and is the simpler solution) or an aggregate (which was not implemented, and expected to have difficulty in implementation). SG9 voted for tuple (the verified solution). SG9 supports the resolution proposed in the NB comment - adopting P2164 to C++23 (with the design guidance - use tuple and not aggregate). Will be passed for LEWG's final decision. The issue was forwarded to LEWG. |
New version: https://isocpp.org/files/papers/D2164R8.pdf |
LEWG discussed R8 of this paper at the 2022-11 Kona meeting (full minutes) and forwarded the paper (with the design recommendation to use PollsPOLL: We want the “aggregate” solution over the “tuple” solution for “P2164: views::enumerate”
Attendance: 25 (20 onsite, 5 on-line) # of Authors: 1xSA Author Position: Consensus against POLL: Apply the resolution of NB comment: “FR#416: FR-014-021 26.6 (range.factories) Add views::enumerate” (duplicate of: “US 48-108 26 [ranges] Add views::enumerate”) (issue: cplusplus/nbballot#416) for C++23
Attendance: 25 (20 onsite, 5 on-line) # of Authors: 1xSF Author Position: Consensus in favor SummaryAuthor will update the paper according to LEWG's design recommendation, the paper will target C++23 (to be confirmed with electronic poll). |
Has the paper been updated already? I need to know if it is ready for
polling
…--
Bryce Adelstein Lelbach aka wash (he/him/his)
US Programming Language Standards Chair
ISO C++ Library Evolution Chair
Principal Architect @ NVIDIA
--
On Thu, Nov 17, 2022, 23:23 Inbal Levi ***@***.***> wrote:
LEWG discussed D8 <https://isocpp.org/files/papers/D2164R8.pdf> of this
paper in Kona2022 meeting (full minutes
<https://wiki.edg.com/bin/view/Wg21kona2022/P2164#Library-Evolution-2022-11-10-13:00-15:00>)
and forwarded the proposed resolution suggested in the paper for C++23.
Polls
*POLL: We want the “aggregate” solution over the “tuple” solution for
“P2164 <https://wg21.link/P2164>: views::enumerate”*
SF F N A SA
1 2 2 6 8
*Attendance:* 25 (20 onsite, 5 on-line)
*# of Authors:* 1xSA
*Author Position:* Consensus against
*POLL: Apply the resolution of NB comment: “FR#416: FR-014-021 26.6
(range.factories) Add views::enumerate” (duplicate of: “US 48-108 26
[ranges] Add views::enumerate”) (issue: cplusplus/nbballot#416
<cplusplus/nbballot#416>) for C++23*
SF F N A SA
6 10 0 2 2
*Attendance:* 25 (20 onsite, 5 on-line)
*# of Authors:* 1xSF
*Author Position:* Consensus in favor
Summary
Author will update the paper according to LEWG's design recommendation,
the paper will target C++23 (to be confirmed with electronic poll).
—
Reply to this email directly, view it on GitHub
<#875 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADBG4XOZE3BEVURED3DDI3WIY5VPANCNFSM4NHBWX6Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Yes.
https://isocpp.org/files/papers/P2164R8.pdf
On Thu, Nov 17, 2022, 13:42 Bryce Adelstein Lelbach aka wash <
***@***.***> wrote:
… Has the paper been updated already? I need to know if it is ready for
polling
--
Bryce Adelstein Lelbach aka wash (he/him/his)
US Programming Language Standards Chair
ISO C++ Library Evolution Chair
Principal Architect @ NVIDIA
--
On Thu, Nov 17, 2022, 23:23 Inbal Levi ***@***.***> wrote:
> LEWG discussed D8 <https://isocpp.org/files/papers/D2164R8.pdf> of this
> paper in Kona2022 meeting (full minutes
> <https://wiki.edg.com/bin/view/Wg21kona2022/P2164#Library-Evolution-2022-11-10-13:00-15:00>)
> and forwarded the proposed resolution suggested in the paper for C++23.
> Polls
>
> *POLL: We want the “aggregate” solution over the “tuple” solution for
> “P2164 <https://wg21.link/P2164>: views::enumerate”*
> SF F N A SA
> 1 2 2 6 8
>
> *Attendance:* 25 (20 onsite, 5 on-line)
>
> *# of Authors:* 1xSA
>
> *Author Position:* Consensus against
>
> *POLL: Apply the resolution of NB comment: “FR#416: FR-014-021 26.6
> (range.factories) Add views::enumerate” (duplicate of: “US 48-108 26
> [ranges] Add views::enumerate”) (issue: cplusplus/nbballot#416
> <cplusplus/nbballot#416>) for C++23*
> SF F N A SA
> 6 10 0 2 2
>
> *Attendance:* 25 (20 onsite, 5 on-line)
>
> *# of Authors:* 1xSF
>
> *Author Position:* Consensus in favor
> Summary
>
> Author will update the paper according to LEWG's design recommendation,
> the paper will target C++23 (to be confirmed with electronic poll).
>
> —
> Reply to this email directly, view it on GitHub
> <#875 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AADBG4XOZE3BEVURED3DDI3WIY5VPANCNFSM4NHBWX6Q>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
P2164R8 views::enumerate (Corentin Jabot) |
LWG reviewed D2164R9 and approved P2164R9 for C++, ship vehicle to be confirmed by LEWG electronic poll.
|
P2164R9 views::enumerate (Corentin Jabot) |
2022-11 Library Evolution Electronic Poll OutcomesPoll 1.1: Send [P2164R8] views::enumerate to Library Working Group for C++23, classified as an addition ([P0592R4] bucket 3 item).
Outcome: Consensus in favor. |
Ship vehicle is confirmed to be c++23 so marking tentatively ready for plenary |
P2164R0 views::enumerate (Corentin Jabot)
The text was updated successfully, but these errors were encountered: