Skip to content

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

Open
wg21bot opened this issue Sep 21, 2024 · 4 comments
Open

P3388 R2 When Do You Know connect Doesn't Throw? #2043

wg21bot opened this issue Sep 21, 2024 · 4 comments
Labels
B1 - focus Bucket 1 as described by P0592: material that is mentioned in this plan. C++26 Targeted at C++26 IS Ship vehicle: IS LWG Library lwg-pending LWG Chair needs to disposition senders/receivers size - medium paper size estimate
Milestone

Comments

@wg21bot
Copy link
Collaborator

wg21bot commented Sep 21, 2024

P3388R0 When Do You Know connect Doesn't Throw? (Robert Leahy)

@wg21bot wg21bot added the LEWG Library Evolution label Sep 21, 2024
@wg21bot wg21bot added this to the 2024-telecon milestone Sep 21, 2024
@inbal2l inbal2l added B1 - focus Bucket 1 as described by P0592: material that is mentioned in this plan. C++26 Targeted at C++26 IS Ship vehicle: IS size - medium paper size estimate ready-for-library-evolution-meeting-review This paper needs to be discussed at a Library Evolution meeting labels Sep 21, 2024
@inbal2l
Copy link
Collaborator

inbal2l commented Dec 15, 2024

2024-11-22 Library Evolution Wroclaw Meeting

P3388R0: When Do You Know connect Doesn't Throw?

2024-11-22 Library Evolution Wroclaw Meeting Minutes

Champion: Robert Leahy
Chair: Fabio Fracassi / Inbal Levi
Minute Taker: Khalil Estell

Summary

POLL: We support design direction that require receivers to be no-throw moveable (P3388R0).

SF F N A SA
8 7 0 0 0

Attendance: 16 (IP) + 4 (R)
Author's Position: SF
Outcome: Strong consensus in favor

POLL: We promise more time to explore options that allows senders to statically determine whether connecting to a receiver will throw.

SF F N A SA
6 8 0 1 0

Attendance: 18 (IP) + 4 (R)
Author's Position: SF
Outcome: Strong consensus in favor

A: I don't think the case was made that we should be working on this over other things.

Next Steps

We 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.

@inbal2l inbal2l added the needs-revision Paper needs changes before it can proceed label Dec 15, 2024
@jensmaurer jensmaurer modified the milestones: 2024-telecon, 2025-telecon Dec 18, 2024
@wg21bot
Copy link
Collaborator Author

wg21bot commented Jan 14, 2025

P3388R1 When Do You Know connect Doesn't Throw? (Robert Leahy)

@wg21bot wg21bot removed the needs-revision Paper needs changes before it can proceed label Jan 14, 2025
@wg21bot wg21bot changed the title P3388 R0 When Do You Know connect Doesn't Throw? P3388 R1 When Do You Know connect Doesn't Throw? Jan 14, 2025
@wg21bot
Copy link
Collaborator Author

wg21bot commented Apr 17, 2025

P3388R2 When Do You Know connect Doesn't Throw? (Robert Leahy)

@wg21bot wg21bot changed the title P3388 R1 When Do You Know connect Doesn't Throw? P3388 R2 When Do You Know connect Doesn't Throw? Apr 17, 2025
@inbal2l
Copy link
Collaborator

inbal2l commented May 5, 2025

2025-04-01 Library Evolution Telecon

P3388R1: When do you know that Connect Doesn’t Throw?

2025-04-01 Library Evolution Hagenberg Minutes

Champion: Robert Leahy
Chair: Inbal Levi
Minute Taker: Mark Hoemmen

Summary

ACTION: 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).

SF F N A SA
8 5 0 0 0

Attendance: 16
Author's Position: SF
Outcome: Strong consensus in favour

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).

SF F N A SA
9 3 0 0 0

Attendance: 16
Author's Position: SF
Outcome: Strong consensus in favour

Next Steps

P3388R1 (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).

@inbal2l inbal2l added LWG Library lwg-pending LWG Chair needs to disposition and removed LEWG Library Evolution ready-for-library-evolution-meeting-review This paper needs to be discussed at a Library Evolution meeting labels May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B1 - focus Bucket 1 as described by P0592: material that is mentioned in this plan. C++26 Targeted at C++26 IS Ship vehicle: IS LWG Library lwg-pending LWG Chair needs to disposition senders/receivers size - medium paper size estimate
Projects
Development

No branches or pull requests

4 participants