`std::make_unique` vs. Manual `std::unique_ptr` Construction: When Should You Use Which?

When to Use std::make_unique Over Manual Construction of std::unique_ptr

The std::make_unique function provides several benefits for constructing unique pointers compared to manually using the new operator and the unique_ptr constructor:

Safety for Creating Temporaries:

• std::make_unique can be safely used to create temporary unique pointers, while explicit use of new requires caution to avoid using unnamed temporaries.

Simplified Syntax:

• make_unique reduces the need for redundant type usage, making code more concise and avoiding the possibility of type mismatches.

Avoidance of Rules for Using new:

• With make_unique, there is no need to remember the rule about "never" using new directly when creating unique pointers. Instead, make_unique can be used as a universal solution.

Potential Enhancements in C 17:

• C 17 may include changes that remove the potential safety concerns associated with directly using new when constructing empty unique pointers. However, make_unique remains the recommended approach for safety and clarity.

In summary, std::make_unique provides benefits in terms of safety, syntax simplification, and adherence to best practices for unique pointer creation. Although it does not offer runtime efficiency advantages like std::make_shared, its use is encouraged for creating unique pointers in modern C code.

The above is the detailed content of `std::make_unique` vs. Manual `std::unique_ptr` Construction: When Should You Use Which?. For more information, please follow other related articles on the PHP Chinese website!