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

This article mainly explains "how C++ gets the ownership of widget". Interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Next, let the editor take you to learn "how C++ takes ownership of widget".

R.32: an attempt to acquire ownership of widget through the unique_ptr type parameter representation function

Reason (reason)

Using unique_ptr in this way forces the transfer of ownership both in terms of documentation and implementation.

Example (sample)

Void sink (unique_ptr); / / takes ownership of the widget

Void uses (widget*); / / just uses the widget

Example, bad (negative example)

Void thinko (const unique_ptr&); / / usually not what you want

Enforcement (implementation recommendations)

(Simple) Warn if a function takes a Unique_pointer parameter by lvalue reference and does not either assign to it or call reset () on it on at least one code path. Suggest taking a T * or T & instead.

(simple) alarm if a function uses the Unique_pointer parameter through a left-value reference but does not assign a value to it, or if reset is called on at least one code path. It is recommended to use T* or T & instead.

(Simple) (Foundation) Warn if a function takes a Unique_pointer parameter by reference to const. Suggest taking a const T * or const T & instead.

(simple) (basic) if a function uses the Unique_pointer parameter as a constant reference, it is recommended to use const T * or const T & instead.

At this point, I believe you have a deeper understanding of "how C++ takes ownership of widget". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

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.