Title
Revert the changes from P0156R0: variadic lock_guard
Status
resolved
Section
[thread.lock.guard]
Submitter
Finland, Great Britain

Created on 2017-02-03.00:00:00 last changed 85 months ago

Messages

Date: 2017-03-15.00:00:00

[ 2017-03-12, post-Kona ]

Resolved by P0156R2.

Date: 2017-02-15.00:00:00

[ 2017-02-02, Marshall notes ]

This was the subject of intense discussion in Issaquah, and a joint LEG/LEWG session agreed on this approach.

Date: 2017-02-03.00:00:00
Addresses FI 8, GB 61

The class template lock_guard was made variadic. This is abi-breaking, and confusing because one-argument lock_guards have a typedef mutex_type but lock_guards with more than one argument don't. There's no need to try to shoehorn this functionality into one type.

Proposed change: Revert the changes to lock_guard, and introduce a new variadic class template vlock_guard that doesn't have the mutex_type typedef at all.

History
Date User Action Args
2017-03-12 23:04:12adminsetmessages: + msg9082
2017-03-12 23:04:12adminsetstatus: new -> resolved
2017-02-04 01:16:32adminsetmessages: + msg8874
2017-02-03 00:00:00admincreate