> On March 19, 2020 at 10:07 AM Jonathan Wakely <jwakely.gcc@xxxxxxxxx> wrote: > > Accidentally creating a temporary unique_lock that immediately goes out of scope? :-) > http://kayari.org/cxx/antipatterns.html#locking-mutex Not that bad I think. :) (The code has been in production on Linux & Windows for years so something like that should've popped up already.) Actually the bad assumption was that my unit tests were doing sufficient testing of my GetThreadId wrapper. That wasn't working properly on Mac but not triggering an error either. The synchronization was not the problem--only the Thread IDs being used as keys into a std::map. Thanks again!
