Notice: This page requires JavaScript to function properly.
Please enable JavaScript in your browser settings or update your browser.
Learn Moving Unique Pointers | Unique Pointers
C++ Smart Pointers
course content

Course Content

C++ Smart Pointers

C++ Smart Pointers

1. Introduction to Smart Pointers
2. Unique Pointers
3. Shared Pointers
4. Weak Pointers
5. Advanced topics

book
Moving Unique Pointers

Copying Not Allowed

A std::unique_ptr is a smart pointer that manages a dynamically allocated object and ensures its proper deletion when it goes out of scope. It has exclusive ownership of the object it manages, meaning no two std::unique_ptr can own the same object simultaneously.

cpp

main

copy
123456789
#include <iostream> #include <memory> int main() { std::unique_ptr<int> first_unique_pointer = std::make_unique<int>(42); // This will cause a compilation error: copying is not allowed std::unique_ptr<int> second_unique_pointer = first_unique_pointer; }

Moving a Unique Pointer

Although copying is not allowed, you can transfer ownership of the object using std::move. This moves the resource from one std::unique_ptr to another, leaving the original pointer empty.

cpp

main

copy
123456789101112131415
#include <iostream> #include <memory> int main() { std::unique_ptr<int> first_unique_pointer = std::make_unique<int>(42); // Transferring ownership using std::move std::unique_ptr<int> second_unique_pointer = std::move(first_unique_pointer); if (!first_unique_pointer) std::cout << "first_unique_pointer is now empty.\n"; std::cout << "second_unique_pointer owns the value: " << *second_unique_pointer << '\n'; }

When you use std::move, ownership of the object is transferred from one unique pointer to another. After this, the original pointer no longer owns the object, and the new pointer becomes its owner.

Task

Swipe to start coding

Complete the following code in a way that the ownership of the dynamically allocated integer (with value 42) is safely transferred from unique_pointer_a to unique_pointer_b.

Solution

cpp

solution

Switch to desktopSwitch to desktop for real-world practiceContinue from where you are using one of the options below
Everything was clear?

How can we improve it?

Thanks for your feedback!

Section 2. Chapter 2
toggle bottom row

book
Moving Unique Pointers

Copying Not Allowed

A std::unique_ptr is a smart pointer that manages a dynamically allocated object and ensures its proper deletion when it goes out of scope. It has exclusive ownership of the object it manages, meaning no two std::unique_ptr can own the same object simultaneously.

cpp

main

copy
123456789
#include <iostream> #include <memory> int main() { std::unique_ptr<int> first_unique_pointer = std::make_unique<int>(42); // This will cause a compilation error: copying is not allowed std::unique_ptr<int> second_unique_pointer = first_unique_pointer; }

Moving a Unique Pointer

Although copying is not allowed, you can transfer ownership of the object using std::move. This moves the resource from one std::unique_ptr to another, leaving the original pointer empty.

cpp

main

copy
123456789101112131415
#include <iostream> #include <memory> int main() { std::unique_ptr<int> first_unique_pointer = std::make_unique<int>(42); // Transferring ownership using std::move std::unique_ptr<int> second_unique_pointer = std::move(first_unique_pointer); if (!first_unique_pointer) std::cout << "first_unique_pointer is now empty.\n"; std::cout << "second_unique_pointer owns the value: " << *second_unique_pointer << '\n'; }

When you use std::move, ownership of the object is transferred from one unique pointer to another. After this, the original pointer no longer owns the object, and the new pointer becomes its owner.

Task

Swipe to start coding

Complete the following code in a way that the ownership of the dynamically allocated integer (with value 42) is safely transferred from unique_pointer_a to unique_pointer_b.

Solution

cpp

solution

Switch to desktopSwitch to desktop for real-world practiceContinue from where you are using one of the options below
Everything was clear?

How can we improve it?

Thanks for your feedback!

Section 2. Chapter 2
Switch to desktopSwitch to desktop for real-world practiceContinue from where you are using one of the options below
We're sorry to hear that something went wrong. What happened?
some-alt