Hi,
As you probably know, Boost.Thread provides a number of generic lock scope guard classes, such as lock_guard< T >,unique_lock< T >,shared_lock< T >,upgrade_lock< T > andupgrade_to_unique_lock< T >, where T is a lockable type. These classes assume presence of the specific member functions in T to perform locking, but some of these functions are not present in TBB mutexes. My current problem is withspin_rw_mutex, which does support shared and upgradable locking but with a different interface. Other TBB mutex types also provide locking with different interfaces, and what's most frustrating is that different mutex types provide same locking functionality through different interfaces (e.g. queueing mutexes have no methods at all).
Could it be done that all TBB mutexes provide the same interface for each particular type of locking, preferably compatible with Boost locks? I realize that in case of queueing mutexes this would not be trivial, I can only think of specializing lock types for these mutexes. These specializations could be placed in a separate header withing compat directory. For other mutexes it seems to suffice to add the required synonym methods for the existing ones (e.g. lock_shared forwarding to lock_read inspin_rw_mutex).
