GB360 32 Consolidate fragmented synchronization headers

cplusplus / nbballot

Handling of NB comments in response to ballots

14 stars 4 forks source link

GB360 32 Consolidate fragmented synchronization headers #356

Closed wg21bot closed 4 years ago

wg21bot commented 4 years ago

Too many new headers The CD includes new headers <stop_token>, <semaphore>, <latch>, and <barrier>. It seems unhelpful to split the synchronization utilities across so many different headers.

Consolidate them into a single <sync> header or similar.

ogiroux commented 4 years ago

Recommend no change in response to GB 360:

stop_token is very seperate from the others.
sync is a bland name that captures almost all SG1 topics.
These facilities are not expected to often be used together (not likely to save I/O).
Merging headers is in conflict with the guidance to avoid huge headers. SF F N A SA 6 7 5 0 0 Unanimous consent.

tituswinters commented 4 years ago

LEWG in Belfast: Rejected. No consensus for change.