On Mon, 8 Sept 2025 at 09:24, Jonathan Wakely <cxx_at_[hidden]> wrote:

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

Although I suppose all the existing xxx_n names in the library have an 'n'
parameter that tells you the length, whereas here it's implied by the
number of template arguments.