Opened 14 years ago

Closed 13 years ago

Last modified 7 years ago

#2638 closed Feature Requests (wontfix)

shared mutex should be recursive

Reported by: mur@… Owned by: Anthony Williams
Milestone: Boost 1.38.0 Component: thread
Version: Boost 1.37.0 Severity: Optimization
Keywords: shared mutex recursive Cc:

Description

shared mutex should be recursive or such a mutex/lock should be added.

Change History (4)

comment:1 by anonymous, 14 years ago

Component: Nonethread
Owner: set to Anthony Williams
Severity: ProblemOptimization

comment:2 by Anthony Williams, 13 years ago

Resolution: wontfix
Status: newclosed

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.

comment:3 by anonymous, 11 years ago

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

comment:4 by anonymous, 7 years ago

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.

Note: See TracTickets for help on using tickets.