Two weeks ago, the ISO C++ standard meeting took place in Jacksonville. Today I want to make a short detour and write about the revolutionary decision that was made in the Jacksonville meeting. Additionally, I refer to the post C++ Will no Longer Have Pointers by Fluent C++. The standard committee decided that pointers will be deprecated in C++20 and will with very high probability be removed in C++23.

To be honest, what seems like a revolution is only the last step in a long evolution. First, let me explain the big picture.

The evolution of pointers in C++

Pointers are part of C++ since the first beginning. We got them from C. From the first beginning there was always the tendency in C++ to make the handling with pointers more type-safe without paying the extra cost.

With C++98 we got std::auto_ptr to express exclusive ownership. But std::auto_ptr had a big issue. When you copy an std::auto_ptr the resource will be moved. What looks like a copy operation was actually a move operation. The graphic shows the surprising behaviour of an std::auto_ptr.

This was extremely bad and the reason for a lot of serious bugs; therefore, we got std::unique_ptr with C++11 and std::auto_ptr was deprecated in C++11 and finally removed in C++17. Additionally, we got std::shared_ptr and std::weak_ptr in C++11 for handling shared ownership. You can not copy but move an std::unique_ptr and if you copy or assign an std::shared_ptr, the internal reference counter will be increased. Have a look here:

Since C++11 C++ has a multithreading library. This makes the handling with std::shared_ptr quite challenging because an std::shared_ptr is per definition shared but not thread-safe. Only the control-block is thread-safe but not the access to its resource. That means, modifying the reference counter is an atomic operation and you have the guarantee that the resource will be deleted exactly once. This is the reason we will get with C++20 atomic smart pointers: std::atomic_shared_ptr and std::atmic_weak_ptr. Read the details in the proposal: Atomic Smart Pointers.

Now to the more interesting part of C++20 and C++23. Pointers will be deprecated in C++20 and removed in C++23. Or to say it with three words: No New New (NNN).

std::unique_ptr to our rescue

But hold, we have a dogma in C++: Don't pay for anything, you don't need. How can we program without a pointer? Just use an std::unique_ptr. An std::unique_ptr is by design as fast and as slim as a raw pointer but has a great benefit: it automatically manages its resource.

The program allocates and deletes 100.000.000 ints. I use a raw pointer, and std::shared_ptr and std::unique_ptr in two variations. I executed the program with and without maximum optimisation on Linux and Windows. Here are the numbers.

Ownership semantic

Honestly, we use pointers and in particular raw pointers far too often. The question if you should use a pointer, boils down to one question: Who is the owner? Luckily, we can directly express our intention about ownership in code.

Local objects. The C++ runtime as the owner automatically manages the lifetime of these resources. The same holds for global objects or members of a class. The guidelines calls them scoped objects.

References: I'm not the owner. I only borrowed the resource that cannot be empty.

Raw pointers: I'm not the owner. I only borrowed the resource that can be can be empty. I must not delete the resource.

std::unique_ptr: I'm the exclusive owner of the resource. I may explicitly release the resource.

std::shared_ptr: I share the resource with other shared ptr. I may explicitly release my shared ownership.

std::weak_ptr: I'm not the owner of the resource but I may become temporary the shared owner of the resource by using the method std::weak_ptr::lock.

We have only to change our practice in one out of six use-cases and we are fine with the next evolution step in C++.

What's next?

Sorry for the detour but the Jacksonville decision was worth a detour. The next post will be about the rules to performance in the C++ Core Guidelines.

Further Information

The decision to the next pdf bundle is made. It will take me about a week to prepare the pdf-bundles. First, I have to look for typos. People already subscribed to my newsletter will get them automatically.

Get your e-book at leanpub:

The C++ Standard Library

Concurrency With Modern C++

Get Both as one Bundle

With C++11,C++14, and C++17 we got a lot of new C++ libraries. In addition, the existing ones are greatly improved. The key idea of my book is to give you the necessary information to the current C++ libraries in about 200 pages.

C++11 is the first C++ standard that deals with concurrency. The story goes on with C++17 and will continue with C++20.

I'll give you a detailed insight in the current and the upcoming concurrency in C++. This insight includes the theory and a lot of practice with more the 100 source files.

Get my books "The C++ Standard Library" (including C++17) and "Concurrency with Modern C++" in a bundle.

In sum, you get more than 550 pages full of modern C++ and more than 100 source files presenting concurrency in practice.

I appreciate a lot the fact that the commitee is working on ways to improve cpp safety, but I think it is an error to deprecate and than later remove pointers. I think a better solution would be to make the compiler accepts pointers only under a certain compilation flags, like, let's "--raw-pointers-on". There will be ALWAYS high speed computation use case where the fast the best. ALWAYS. If guy from, let's say, MISRA don't like pointers, just tell them to put this flag on their rules.