100% Free Forever
AI-Powered Learning
Industry Expert Content
Certificates & Badges
Learn At Your Own Pace

C++ Smart Pointers Cheat Sheet

C++ Smart Pointers Cheat Sheet

Covers unique_ptr, shared_ptr, and weak_ptr semantics, ownership models, custom deleters, and how to avoid reference-cycle memory leaks.

2 PagesIntermediateApr 12, 2026

std::unique_ptr

Exclusive ownership smart pointer with zero overhead.

cpp
#include <memory>std::unique_ptr<int> p = std::make_unique<int>(42);  // preferred over newstd::cout << *p;std::unique_ptr<int> p2 = std::move(p);   // ownership transferred, p is now null// std::unique_ptr<int> p3 = p2;          // compile error: copying is disabledvoid takeOwnership(std::unique_ptr<int> ptr) { /* ... */ }takeOwnership(std::move(p2));             // must move, cannot copy// custom deleterstd::unique_ptr<FILE, decltype(&fclose)> file(fopen("f.txt", "r"), &fclose);

std::shared_ptr

Reference-counted shared ownership smart pointer.

cpp
std::shared_ptr<int> a = std::make_shared<int>(10);  // preferred: single allocationstd::shared_ptr<int> b = a;      // both share ownership, use_count() == 2std::cout << a.use_count();      // 2a.reset();                        // a releases its reference; count -> 1// object is destroyed only when the last shared_ptr is destroyed/resetstd::shared_ptr<int> c(new int(5), [](int* p) {    std::cout << "custom delete\n";    delete p;});

std::weak_ptr

Non-owning observer of a shared_ptr that breaks reference cycles.

cpp
std::shared_ptr<int> sp = std::make_shared<int>(99);std::weak_ptr<int> wp = sp;       // does not increase use_countif (auto locked = wp.lock()) {    // returns a shared_ptr, or nullptr if expired    std::cout << *locked;} else {    std::cout << "expired";}std::cout << wp.expired();        // true if the managed object was already destroyed

Avoiding Cyclic References

Break shared_ptr reference cycles that leak memory.

cpp
struct Node {    std::shared_ptr<Node> next;    std::weak_ptr<Node> prev;    // weak_ptr breaks the cycle};auto a = std::make_shared<Node>();auto b = std::make_shared<Node>();a->next = b;b->prev = a;   // if this were shared_ptr, a and b would leak forever

Smart Pointer Comparison

When to reach for each smart pointer type.

  • unique_ptr- Sole owner, move-only, no runtime overhead versus a raw pointer; the default choice.
  • shared_ptr- Multiple owners via atomic reference counting; has overhead from the control block.
  • weak_ptr- Non-owning reference to a shared_ptr-managed object; used to break cycles or observe without extending lifetime.
  • make_unique / make_shared- Preferred factory functions; exception-safe and, for shared_ptr, allocate object + control block in one block.
  • Raw pointer- Still fine for non-owning, non-nullable observation where lifetime is guaranteed by the caller.

enable_shared_from_this

Safely hand out a shared_ptr to 'this' from inside a member function.

cpp
class Session : public std::enable_shared_from_this<Session> {public:    std::shared_ptr<Session> getShared() {        return shared_from_this();   // shares the SAME control block as the original    }    void registerCallback(std::function<void()>& cb) {        // capture a shared_ptr, not 'this', so the object outlives the async op        cb = [self = shared_from_this()] { self->onEvent(); };    }    void onEvent() { /* ... */ }};// WRONG: calling shared_from_this() before any shared_ptr owns the object throws// std::bad_weak_ptr - the object must already be managed via make_shared.

Aliasing Constructor

Point a shared_ptr at a subobject while sharing the parent's control block.

cpp
struct Widget { int id; std::string name; };auto owner = std::make_shared<Widget>(Widget{1, "gizmo"});// aliasing constructor: keeps 'owner's control block alive, but *points* at &owner->namestd::shared_ptr<std::string> namePtr(owner, &owner->name);owner.reset();               // Widget is NOT destroyed yet -std::cout << *namePtr;       // namePtr still keeps it alive; prints "gizmo"// common use: exposing a member of a pimpl-managed object without exposing the whole type

unique_ptr with Arrays and Polymorphic Deletion

Handle array ownership and ensure base-class destructors run correctly.

cpp
// array specialization calls delete[] automaticallystd::unique_ptr<int[]> arr = std::make_unique<int[]>(10);arr[3] = 42;// storing a derived object through a unique_ptr<Base> REQUIRES a virtual destructor,// otherwise only Base::~Base runs and Derived's resources leakstruct Base { virtual ~Base() = default; };struct Derived : Base { std::vector<int> data{1, 2, 3}; };std::unique_ptr<Base> p = std::make_unique<Derived>();p.reset();   // safe: virtual dtor ensures ~Derived runs first// covariant return with unique_ptr (C++14+)struct Cloneable { virtual std::unique_ptr<Cloneable> clone() const = 0; virtual ~Cloneable() = default; };

Control Block Layout & Cost

Understand what make_shared actually allocates and why it matters for weak_ptr lifetime.

cpp
// make_shared allocates ONE block: [control block | T object] contiguouslyauto sp = std::make_shared<int>(5);// shared_ptr(new T(...)) allocates TWO separate blocks: object, then control blockstd::shared_ptr<int> sp2(new int(5));   // extra allocation + worse cache locality// gotcha: with make_shared, the T's memory is NOT freed until the control block// itself is freed - i.e. until the LAST weak_ptr also disappears, not just the// last shared_ptr. A long-lived weak_ptr can keep a large object's memory pinned.std::weak_ptr<int> wp = sp;sp.reset();          // int's destructor runs now...// ...but the underlying storage for the control block + int stays allocated// until wp itself is destroyed, because they share one allocation.

Advanced Pitfalls & Idioms

Issues that surface once smart pointers are used beyond toy examples.

  • std::shared_ptr Thread Safety- The control block's refcount is atomic (safe to copy/destroy from multiple threads), but the pointee itself is NOT synchronized - concurrent writes to *sp still need a mutex.
  • Pimpl with unique_ptr- A class holding std::unique_ptr<Impl> to an incomplete type must declare (not =default in the header) its destructor, or the implicit inline destructor fails to compile against the incomplete type.
  • shared_ptr<void>- Type-erases the deleter while keeping it callable; used to store heterogeneous owned resources, e.g. in a cache keyed by name.
  • std::enable_shared_from_this pitfall- Calling shared_from_this() on an object not already owned by a shared_ptr throws std::bad_weak_ptr; never call it from a constructor.
  • owner_before- Ordering comparator on shared_ptr/weak_ptr based on control-block identity rather than pointer value; needed to put weak_ptrs in an ordered set/map.
  • std::atomic<std::shared_ptr<T>> (C++20)- Standard atomic specialization for safely swapping a shared_ptr itself across threads, replacing the deprecated std::atomic_load/store free functions.
Pro Tip

Never construct two independent shared_ptrs from the same raw pointer - each gets its own control block and the object gets double-deleted; always copy an existing shared_ptr instead of wrapping the same raw pointer twice.

Was this cheat sheet helpful?

Explore Topics

#CSmartPointers#CSmartPointersCheatSheet#Programming#Intermediate#StdUniquePtr#StdSharedPtr#StdWeakPtr#AvoidingCyclicReferences#CheatSheet#SkillVeris

Frequently Asked Questions

21 categories · pick one to explore

Does SkillVeris have a tech blog, and what does it cover?
Yes, the SkillVeris blog has over 500 articles covering AI and machine learning, programming, web development, DevOps, cloud, security, databases and career guidance. Articles are practical and answer-first, and many use the Learn Through Hobbies approach, teaching technical concepts through cricket, music, gaming or cooking analogies. Everything is free to read.
What is the SkillVeris tech glossary and how big is it?
The SkillVeris glossary is a free reference of roughly 2,000-plus technology terms, each with a clear plain-language definition. It spans AI, programming, web, DevOps, cloud, security and database vocabulary, so whenever a lesson, article or job description uses jargon you do not recognise, the glossary gives you a fast, reliable answer.
Are the developer cheat sheets on SkillVeris free to download?
The cheat sheets are completely free to use, like everything else on SkillVeris. Each sheet condenses a language or tool into its essential syntax, commands and patterns for quick reference while coding. They are designed for rapid lookup during real work, complementing the deeper explanations found in study notes and courses.
Which programming references and cheat sheets are available?
Cheat sheets cover the platform's main domains, including programming languages, AI and ML tooling, web development, DevOps, cloud, security and databases, matching the topics of the 37 live courses. Each sheet lists related reading links and hashtags, so you can jump from a quick reference into fuller study notes or blog articles.
How do I find the meaning of a technical term quickly?
Search the SkillVeris glossary, which holds around 2,000-plus terms with concise, plain-language definitions. Each entry gets to the point in its first sentence, then links to related reading like blog posts or study notes for deeper context. It is faster and more consistent than sifting through scattered search results.
Is the SkillVeris blog good for beginners learning to code?
Yes, many blog articles are written specifically for beginners, and the Learn Through Hobbies style makes them unusually approachable: you might learn Python concepts through cricket or understand APIs through cooking. With 500-plus articles across skill levels, beginners can start with fundamentals and keep reading as they advance, entirely free.
Can cheat sheets replace full courses for learning a language?
No, cheat sheets are references, not teaching tools; they assume you already understand the concepts and just need syntax or commands fast. To actually learn a language, take a structured SkillVeris course with its 24–40 lessons and assessments, then keep the cheat sheet beside you while practising in Code Lab.
How often are new blog articles published on SkillVeris?
The blog grows regularly and already exceeds 500 articles, with new posts added as courses launch and technologies evolve. Topics track the platform's catalogue across AI, programming, web development, DevOps, cloud and security, so checking the Blog section periodically surfaces fresh tutorials, explainers and career-focused pieces, all free to read.
Does the glossary cover AI and machine learning terms?
Yes, AI and machine learning vocabulary is a major part of the roughly 2,000-plus term glossary, covering everything from foundational terms to modern concepts around LLMs, RAG and MLOps. Definitions are plain-language and answer-first, which helps when dense AI papers or course lessons throw unfamiliar jargon at you.
Are there cheat sheets for interview preparation?
Cheat sheets work well as interview-day refreshers because they compress syntax, commands and key concepts into scannable references. For dedicated preparation, combine them with the SkillVeris interview questions feature, which includes readiness scoring, plus study notes for depth. Reviewing a relevant cheat sheet just before an interview steadies recall under pressure.
Can I read the tech blog without signing up?
Yes, the blog is freely readable, and SkillVeris never charges for content. All 500-plus articles are open, covering tutorials, concept explainers and career advice. Creating a free account adds value elsewhere on the platform, like course progress tracking and certificates, but reading the blog requires no commitment at all.
How is the SkillVeris glossary different from Wikipedia?
The glossary is purpose-built for learners: definitions are short, plain-language and answer-first, sized for a quick lookup mid-lesson rather than a deep encyclopedic read. Entries also cross-link to related SkillVeris study notes, blog posts and courses, so a definition becomes a doorway into structured learning instead of a dead end.
Do blog articles use the Learn Through Hobbies method?
Many blog articles teach technical topics through hobby analogies, a hallmark of the SkillVeris blog, so you will find articles explaining programming through cricket, machine learning through music, or system design through cooking. The analogy is the teaching device; the article still delivers the real technical concept underneath.
Where can I find quick programming references while coding?
Open the SkillVeris cheat sheets, which are built exactly for that moment: compact, scannable references for syntax, commands and common patterns across languages and tools. Keep the relevant sheet in a browser tab while you work in Code Lab or your own editor, and dip into the glossary for terminology.
Is there a glossary entry for terms I meet in job descriptions?
Very likely yes, with roughly 2,000-plus terms across AI, programming, web, DevOps, cloud, security and databases, the glossary covers most jargon that appears in tech job descriptions. Decoding a listing this way helps you judge role fit honestly and prepares you to discuss those terms in interviews.
Are the blog articles written for the Indian tech audience?
The blog serves Indian learners plus a worldwide audience. Content stays globally relevant while acknowledging realities that matter in India, such as free access being essential for students and freshers, and career guidance that connects naturally to the SkillVeris jobs portal, which aggregates roles across India, UK, USA, Germany and Remote.
Can I suggest a topic for the blog or glossary?
SkillVeris content grows in response to what learners need, so feedback is welcome through the platform's support channels. If a term is missing from the glossary or a topic deserves an article, telling the team helps prioritise it. Meanwhile, the AI Mentor can answer the question immediately, 24/7, at any depth.
Do cheat sheets and glossary entries link to deeper learning?
Yes, every cheat sheet and glossary entry carries related reading links into study notes, blog articles and courses, plus concept hashtags for discovering similar content. This cross-linking means a thirty-second lookup can smoothly become a structured learning session whenever you decide you want more than a quick answer.
What makes SkillVeris programming references trustworthy?
The references are written to strict internal quality standards, kept consistent with the platform's 37 live courses, and never padded with invented statistics or hype. Definitions and cheat sheets are reviewed against the same content contracts that govern courses, and the answer-first style makes any inaccuracy easy to spot and correct.
How do the blog, glossary and cheat sheets fit into my learning routine?
Use them as satellites around your main course: read blog articles for context and motivation, hit the glossary the instant jargon appears, and keep cheat sheets open while coding. Together with study notes, Code Lab and the 24/7 AI Mentor, they turn passive reading into a complete, free learning system.

What Learners Say

Real journeys from the SkillVeris community — swipe for more.

SkillVeris taught me Python through Cricket. Now I’m building real projects and feeling confident!
Arjun S. · B.Tech Student
The best platform for hobby-based learning. Concepts finally stick.
Priya R. · Data Analyst
I went from zero coding to a portfolio of projects — all by learning through my love for gaming. Landed my first internship!
Kabir M. · CS Undergraduate
Trending Topics50 popular tags — tap to explore
Trending CoursesAll 37 free courses — tap to browse