Boost C++ Libraries: Ticket #2638: shared mutex should be recursive

component, severity changed; owner set

anonymous — Mon, 05 Jan 2009 13:29:52 GMT

owner set to Anthony Williams
component None → thread
severity Problem → Optimization

status changed; resolution set

Anthony Williams — Fri, 29 May 2009 11:00:32 GMT

status new → closed
resolution → wontfix

I consider recursive mutexes in general as undesirable. A recursive shared mutex would be particularly complex, and usage likely error prone due to the interaction between readers and writers. I have no intention of providing such an implementation.

anonymous — Sat, 05 Nov 2011 23:23:20 GMT

whyyyyyyyyyy shit so I'm used to do it by my own

anonymous — Thu, 07 Apr 2016 14:19:44 GMT

Such arrogance !! as if because you think one way the rest of the community can only be wrong. What about lock elevation and its reverse ? even windows natively implements an efficient recursive elevateable read/write lock ... but I guess it too complicated for boost developers so we should all do the work ourselves. Much less use is a timed mutex perhaps if that "complication" was removed it would be less "complex" to implement a useful semantic ?

Yes ... people ... roll your own don't wait as even in C++!4 there isn't one.