Shulou(Shulou.com)06/01 Report--

This article introduces the knowledge of "how C++ defines mutex and protected data together". Many people will encounter this dilemma in the operation of actual cases, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

CP.50: define mutex with protected data, if possible, using the

Synchronized_valueReason (reason)

It should be obvious to a reader that the data is to be guarded and how. This decreases the chance of the wrong mutex being locked, or the mutex not being locked.

The fact that data is protected and how it is protected should be obvious to the reader of the code. This reduces the possibility of locking the wrong mutex or not locking the correct mutex.

Using a synchronized_value ensures that the data has a mutex, and the right mutex is locked when the data is accessed. See the WG21 proposal to add synchronized_value to a future TS or revision of the C++ standard.

Using synchronized_value ensures that the data is locked and the correct mutex is locked when the data is accessed. See WG21 that intends to add synchronized_value functionality to a future technical specification or a version of C++.

Example (sample)

Struct Record {

Std::mutex m; / / take this mutex before accessing other members

/ /...

}

Class MyClass {

Struct DataRecord {

/ /...

}

Synchronized_value data; / / Protect the data with a mutex

This is the content of "how C++ defines mutex and protected data together". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.