-
Notifications
You must be signed in to change notification settings - Fork 1
P3388 R2 When Do You Know connect Doesn't Throw? #2043
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
Comments
2024-11-22 Library Evolution Wroclaw MeetingP3388R0: When Do You Know connect Doesn't Throw? 2024-11-22 Library Evolution Wroclaw Meeting Minutes Champion: Robert Leahy SummaryPOLL: We support design direction that require receivers to be no-throw moveable (P3388R0).
Attendance: 16 (IP) + 4 (R) POLL: We promise more time to explore options that allows senders to statically determine whether connecting to a receiver will throw.
Attendance: 18 (IP) + 4 (R) A: I don't think the case was made that we should be working on this over other things. Next StepsWe support requiring receivers to be no-throw moveable, and promise more time to explore options that allows senders to statically determine whether connecting to a receiver will throw. The paper will need to return to LEWG with wording for the supported solution. |
P3388R1 When Do You Know connect Doesn't Throw? (Robert Leahy) |
P3388R2 When Do You Know connect Doesn't Throw? (Robert Leahy) |
2025-04-01 Library Evolution TeleconP3388R1: When do you know that Connect Doesn’t Throw? 2025-04-01 Library Evolution Hagenberg Minutes Champion: Robert Leahy SummaryACTION: Modify the wording “if there exists a subexpression rcvr2” into “if there exists an expression rcvr2” POLL: Apply the wording fix described above and approve the design and wording as described in P3388R1 and forward to LWG for C++29 (with a recommendation to apply as a DR).
Attendance: 16 POLL: Apply the wording fix described above and approve the design and wording as described in P3388R1 and forward to LWG for C++26 (non-binding, if possible considering LWG’s queue).
Attendance: 16 Next StepsP3388R1 (with minor wording fix) was forwarded to LWG for C++29 and as a DR for C++26 (if possible considering LWG’s queue, we recommend it to be applied on 26 directly, non-binding). |
P3388R0 When Do You Know connect Doesn't Throw? (Robert Leahy)
The text was updated successfully, but these errors were encountered: