#2638 closed Feature Requests (wontfix)
shared mutex should be recursive
| Reported by: | 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 , 14 years ago
| Component: | None → thread |
|---|---|
| Owner: | set to |
| Severity: | Problem → Optimization |
comment:2 by , 13 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:4 by , 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.

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.