> It sounds like ... std::lock_guard with extra steps. I'm not the previous poster, but I think they are still suggesting that the value not be accessible unti

> It sounds like ... std::lock_guard with extra steps. I'm not the previous poster, but I think they are still suggesting that the value not be accessible until the lock is acquired. Something like this (Apologies, I haven't done C++ is a long time and this is just off the top of my head. It's based on the example from the lock_guard example for the sake of comparison): guardthing<int> guarded_value; void safe_increment() { auto lock = guarded_value.lock(); lock.value += 1; std::cout << "value: " << value << "; in thread #" << std::this_thread::get_id() << '\n'; // the mutex in guarded_value is automatically released when lock // goes out of scope }