Il 29/06/23 02:32, Breno Guimarães via Std-Proposals ha scritto:
> There is merit in being able to choose the mutex though.
>
> There are mutexes with deadlock detection instrumentation. Others have
> specialized optimizations for certain workloads.
> Others would expose shared/unique locking interfaces.
>
> I say this because I work in an application that makes use of all those
> types.
>
> It also allows for recursive_mutex, and we do use it, but we are not
> proud of it :)

For some reason, synchronized_value in Boost allows the choice of the
mutex type, but the one in the Concurrency TS doesn't. Does anyone know
the reason?

Boost:
   template<typename T, typename Lockable = mutex>
   class synchronized_value;

Concurrency:
   template<class T>
   class synchronized_value;

Thanks,

-- 
Giuseppe D'Angelo