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

This article mainly explains "how C++ treats link threads as normalized containers". The explanation in this article is simple and clear and easy to learn and understand. let's study and learn "how C++ treats link threads as normalized containers". Let's study and learn together.

CP.23: think of join threads as normalized containers

Reason (reason)

To maintain pointer safety and avoid leaks, we need to consider what pointers are used by a thread. If a thread joins, we can safely pass pointers to objects in the scope of the thread and its enclosing scopes.

To keep pointers safe and avoid leaks, we need to consider which pointers are used by threads. If there is a thread link, we can safely pass the pointer to the object within the thread scope and close the scope.

Example (sample)

Void f (int* p)

{

/ /...

* p = 99

/ /...

}

Int glob = 33

Void some_fct (int* p)

{

Int x = 77

Joining_thread T0 (f, & x); / / OK

Joining_thread T1 (f, p); / / OK

Joining_thread T2 (f, & glob); / / OK

Auto Q = make_unique (99)

Joining_thread T3 (f, q.get ()); / / OK

/ /...

}

Gsl::joining_thread is a std::thread that calls the destructor of joins and cannot be detatched. What we mean by the word "OK" is that as long as the thread that uses the pointer exists, the object that the pointer points to will remain in range (and remain available). Here, the fact that threads are concurrent does not affect life cycle or ownership issues; you can think of a thread as a function object called by somt_ft.

Enforcement (implementation recommendations)

Ensure that joining_threads don't detach (). After that, the usual lifetime and ownership (for local objects) enforcement applies.

Make sure that the connecting thread will not be detach. Then confirm that the usual life cycle and ownership principles (for local objects) are applied.

Thank you for your reading. the above is the content of "how C++ regards a thread of connection as a container of normalization". After the study of this article, I believe you have a deeper understanding of the problem of how C++ treats thread of connection as a container of normalization, and its specific use still needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

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.