The current "fair" shared_mutex implementation is great in the sense 
that it neither favors readers nor writers. This is probably a good 
property in most situations.<br><br>However, there are situations where 
either reader or writer prioritization can be beneficial. In particular,
 I&#39;m working on a project where the locking could be significantly 
stricter without risking introducing deadlocks if read-locks could be 
guaranteed to have priority over write-locks. I fully understand that a read- or 
write-priority implementation might have a bigger overhead compared to 
the existing &quot;fair&quot; shared_mutex implementation, but that is unlikely to
 be a problem for me.<br>
<br>Is anyone in the boost community experiencing similar problems 
and/or is there any interest in extending shared_mutex with support for 
different priority policies?<br><br>
<br>Thanks in advance,<br>Fredrik Orderud