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
LWG3714 Non-single-argument constructors for range adaptors should not be explicit #1257
Comments
2022-07-19 Library Evolution TeleconLWG3714: Non-single-argument constructors for range adaptors should not be explicit 2022-07-19 Library Evolution Telecon Minutes Chair: Billy Baker Minute Taker: Champion: Hewill Kang SummaryThe topic was presented in the LEWG 2022-07-19 telecon. For consistency, the views listed in the issue as well as views that are in flight such as P2374 cartesian_product_view need to be reviewed. There was some previous discussion on the topic of explicit constructors for P1899 stride_view. The issue has been referred to the Ranges Study group for guidance. Next StepsSend the issue to the Ranges study group for further review. |
Scheduled for SG9 on 10-10-2022 (Agenda) |
SG9 (Ranges) reviewed the issue on 2022-10-10, the review included Ville's paper on the same subject PXXXXR0: Ruminations on explicit multi-param constructors of views (Full Minutes). PollsPOLL: We support applying “LWG3714: Non-single-argument constructors for range adaptors should not be explicit” AKA option 2 in Ville’s paper: “Drop the explicit from the C++23 views” to C++23 (possibly as an NB comment, if needed)
Attendance: 10 Author’s position: SF Outcome: Weak recommendation in favor (no consensus) POLL: We support apply option 1 in Ville’s paper: “Make the C++20 view multi-param constructors explicit too” to C++20
Attendance: 10 Author’s position: WF Outcome: Consensus in favor SummaryThe second poll had more consensus. The polls indicate that SG9 support making the C++20 view multi-param constructors explicit (as a C++20 DR / Fix), recommendation is passed to LEWG. |
LEWG discussed this issue (along with P2711 Ruminations on explicit multi-param constructors of views) (full minutes) and decided to reject the resolution. |
@JeffGarland can you close this LWG issue, as we're proceeding with P2711. |
Issue: https://cplusplus.github.io/LWG/issue3714
During the LWG prioritization poll it was suggested that we need LEWG to decide on a consistent policy before we can make any consistency fix here. Please take a look and let us know what LEWG wants here.
The text was updated successfully, but these errors were encountered: