This is a class that encapsulates the critical section. So it is more convenient to lock your resource accessed by multiple threads.
You should use this class as following:
The lock operation is excuted when constructing the lock object. If the code goes out of the range "{}", the lock will be destructed so that the unlock is excuted.
Here I want to stress the two reasons why to lock the resource: one is to avoid the conflict that two threads write the resource at the same time, the other is that one thread reads the resource while it's not desirable for another thread to write it so that the result read is uncertian.
Once I saw one of my colleagues use the lock as follow:(to be continued)
As you see, he protect the operation of retrieving the iterator, but there is no protect on the assignment. Whereas the assignment is also the operation that can arise the synchronized problem. So it's important to know exactly which resource to protect.