Can I use it with std::shared_lock?

________________________________
From: Std-Proposals <std-proposals-bounces_at_[hidden]> on behalf of Ville Voutilainen via Std-Proposals <std-proposals_at_[hidden]>
Sent: Monday, September 8, 2025 6:12:06 PM
To: std-proposals_at_[hidden] <std-proposals_at_[hidden]>
Cc: Ville Voutilainen <ville.voutilainen_at_[hidden]>
Subject: Re: [std-proposals] P3833R0a - std::unique_multilock

On Mon, 8 Sept 2025 at 19:06, Ted Lyngmo via Std-Proposals
<std-proposals_at_[hidden]> wrote:
>
> 2025-09-08 10:51, Jonathan Wakely:
> > > 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.
> Yes, but it may be better to have `unique_lock` first in the name like
> in unique_lock_n. Perhaps spelling it out to not make people think _n
> means a numeric argment would be good:
>
> unique_lock_many
> unique_lock_multi
>
> ... or some version of that? / Ted

I find unique_multilock a perfectly good name.

--
Std-Proposals mailing list
Std-Proposals_at_[hidden]
https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals