A mutex we use has a strange interface (weird casing for example). Having a specialization for std::unique_lock
would help reduce the cognitive overhead of using this mutex.
I couldn't find anything in the standard that specifically allowed specializing std::unique_lock
. Thinking about it, I don't see any downsides off the top of my head to allowing specializations of std::unique_lock
. Can someone confirm that it is indeed unspecified by the standard (and thus undefined behavior following the quote here https://stackoverflow.com/a/8513497)?
If it is permitted, could someone point me to the section in the standard that says that?