std::unique_ptr: Exclusive Ownership and std::make_unique0%

std::shared_ptr: Shared Reference-Counted Ownership and std::make_shared

std::unique_ptr: Exclusive Ownership and std::make_unique

Advanced13 min read•Updated: 2026-10-22

🔒 std::unique_ptr: Exclusive Ownership and std::make_unique

Introduction

std::unique_ptr is the default smart pointer in Modern C++. It guarantees exclusive ownership of a heap-allocated resource: exactly one unique_ptr owns the resource at any given moment, and when that pointer leaves scope, the memory is deleted automatically with zero runtime overhead compared to raw pointers.

🚫 Move-Only Semantics

A std::unique_ptr cannot be copied (copy constructor is deleted to prevent double-free bugs), but it can be moved:

1#include <iostream>
2#include <memory>
3#include <string>
4 
5class UserSession {
6public:
7    std::string username;
8    explicit UserSession(std::string name) : username(std::move(name)) {
9        std::cout << "[LOGIN]: UserSession created for " << username << "\n";
10    }
11    ~UserSession() {
12        std::cout << "[LOGOUT]: UserSession destroyed for " << username << "\n";
13    }
14};
15 
16int main() {
17    // Modern C++14 std::make_unique: Exception-safe heap construction
18    auto sessionPtr = std::make_unique<UserSession>("sumit_msk");
19 
20    // sessionPtr->username; // Access using pointer arrow syntax
21 
22    // auto copySession = sessionPtr; // 💥 Compiler halts: Copying is forbidden!
23    
24    // Transferring ownership via move semantics:
25    std::unique_ptr<UserSession> newOwner = std::move(sessionPtr);
26 
27    if (!sessionPtr) {
28        std::cout << "Original sessionPtr is now null (ownership relinquished).\n";
29    }
30 
31    std::cout << "New owner username: " << newOwner->username << "\n";
32 
33    return 0;
34} // newOwner goes out of scope here: destructor cleanly executes!

💡 Why Prefer `std::make_unique` Over `new`?

1
Prevents memory leaks if an exception is thrown in a multi-argument function call.
2
Eliminates repetitive type declarations (auto p = std::make_unique<Student>() instead of std::unique_ptr<Student> p(new Student())).

Next Lesson

std::shared_ptr: Shared Reference-Counted Ownership and std::make_shared

Continue learning with hands-on practice, examples, and exercises in the upcoming topic.

Related Lessons

Previous Lesson	Next Lesson
Resource Acquisition Is Initialization (RAII) Principle	std::shared_ptr: Shared Reference-Counted Ownership and std::make_shared

Practice Quiz

Test your understanding of this lesson with 1 questions. Each question has one correct answer.

Previous Next

PreviousPrevNext

MSK Institute • Shikohabad

Loading Page Content...

Preparing courses, live labs, and learning resources.सामग्री लोड हो रही है, कृपया प्रतीक्षा करें...

Connecting serverPlease wait...

💻 Practical Labs🚀 Free Demo📜 Verified Certificates

std::shared_ptr: Shared Reference-Counted Ownership and std::make_shared

std::unique_ptr: Exclusive Ownership and std::make_unique

Advanced13 min read•Updated: 2026-10-22

Study Materials

🔒 std::unique_ptr: Exclusive Ownership and std::make_unique

Introduction

🚫 Move-Only Semantics

A std::unique_ptr cannot be copied (copy constructor is deleted to prevent double-free bugs), but it can be moved:

1#include <iostream>
2#include <memory>
3#include <string>
4 
5class UserSession {
6public:
7    std::string username;
8    explicit UserSession(std::string name) : username(std::move(name)) {
9        std::cout << "[LOGIN]: UserSession created for " << username << "\n";
10    }
11    ~UserSession() {
12        std::cout << "[LOGOUT]: UserSession destroyed for " << username << "\n";
13    }
14};
15 
16int main() {
17    // Modern C++14 std::make_unique: Exception-safe heap construction
18    auto sessionPtr = std::make_unique<UserSession>("sumit_msk");
19 
20    // sessionPtr->username; // Access using pointer arrow syntax
21 
22    // auto copySession = sessionPtr; // 💥 Compiler halts: Copying is forbidden!
23    
24    // Transferring ownership via move semantics:
25    std::unique_ptr<UserSession> newOwner = std::move(sessionPtr);
26 
27    if (!sessionPtr) {
28        std::cout << "Original sessionPtr is now null (ownership relinquished).\n";
29    }
30 
31    std::cout << "New owner username: " << newOwner->username << "\n";
32 
33    return 0;
34} // newOwner goes out of scope here: destructor cleanly executes!

💡 Why Prefer `std::make_unique` Over `new`?

1
Prevents memory leaks if an exception is thrown in a multi-argument function call.
2
Eliminates repetitive type declarations (auto p = std::make_unique<Student>() instead of std::unique_ptr<Student> p(new Student())).

Next Lesson

std::shared_ptr: Shared Reference-Counted Ownership and std::make_shared

Continue learning with hands-on practice, examples, and exercises in the upcoming topic.

Related Lessons

Previous Lesson	Next Lesson
Resource Acquisition Is Initialization (RAII) Principle	std::shared_ptr: Shared Reference-Counted Ownership and std::make_shared

Practice Quiz

Test your understanding of this lesson with 1 questions. Each question has one correct answer.

Previous Next

🔒 std::unique_ptr: Exclusive Ownership and std::make_unique

Introduction

🚫 Move-Only Semantics

💡 Why Prefer std::make_unique Over new?

std::shared_ptr: Shared Reference-Counted Ownership and std::make_shared

Related Lessons

Practice Quiz

Loading Page Content...

🔒 std::unique_ptr: Exclusive Ownership and std::make_unique

Introduction

🚫 Move-Only Semantics

💡 Why Prefer std::make_unique Over new?

std::shared_ptr: Shared Reference-Counted Ownership and std::make_shared

Related Lessons

Practice Quiz

💡 Why Prefer `std::make_unique` Over `new`?

💡 Why Prefer `std::make_unique` Over `new`?