Date: Mon, 8 Sep 2025 09:24:35 +0100
On Sun, 7 Sept 2025 at 14:23, Ted Lyngmo via Std-Proposals <
std-proposals_at_[hidden]> wrote:
> Thanks to you too Tiago!
>
> You touched upon something I meant to ask for. A name. unique_multilock
> felt right at the time I started because it is supposed to be ju like a
> unique_lock, only for multiple lockables.
>
> Today we have lock_guard and it's multi mutex cousin scoped_lock.
> With this proposal we'd have unique_lock and ...
>
> Some candidates, other than unique_multilock:
> unique_scoped_lock ("scoped" didn't feel right for this movable type)
> unique_lock_set (the "set" part didn't feel right)
>
> If anyone has an idea, please share!
>
unique_lock_n seems fairly easy to guess what it does from the name.
std-proposals_at_[hidden]> wrote:
> Thanks to you too Tiago!
>
> You touched upon something I meant to ask for. A name. unique_multilock
> felt right at the time I started because it is supposed to be ju like a
> unique_lock, only for multiple lockables.
>
> Today we have lock_guard and it's multi mutex cousin scoped_lock.
> With this proposal we'd have unique_lock and ...
>
> Some candidates, other than unique_multilock:
> unique_scoped_lock ("scoped" didn't feel right for this movable type)
> unique_lock_set (the "set" part didn't feel right)
>
> If anyone has an idea, please share!
>
unique_lock_n seems fairly easy to guess what it does from the name.
Received on 2025-09-08 08:24:54