Built and tested on:

• Linux (GCC/clang)
• Windows (MSVC 32/64)
• MacOS (clang)
• WebAssembly (Emscripten)

This is a small header-only library, providing the unique-ownership smart pointers observable_unique_ptr and observable_sealed_ptr that can be observed with non-owning pointers observer_ptr. This is a mixture of std::unique_ptr and std::shared_ptr: it borrows the unique-ownership semantic of std::unique_ptr (movable, non-copiable), but allows creating observer_ptr to monitor the lifetime of the pointed object (like std::weak_ptr for std::shared_ptr).

The only difference between observable_unique_ptr and observable_sealed_ptr is that the former can release ownership, while the latter cannot. Disallowing release of ownership enables allocation optimizations. Therefore, the recommendation is to use observable_sealed_ptr unless release of ownership is required.

These pointers are useful for cases where the shared-ownership of std::shared_ptr is not desirable, e.g., when lifetime must be carefully controlled and not be allowed to extend, yet non-owning/weak/observer references to the object may exist after the object has been deleted.

Note: Because of the unique ownership model, observer pointers cannot extend the lifetime of the pointed object, hence this library provides less thread-safety compared to std::shared_ptr/std::weak_ptr. This is also true of std::unique_ptr, and is a fundamental limitation of unique ownership. If this is an issue, you will need either to add your own explicit locking logic, or use std::shared_ptr/std::weak_ptr.

This is a header-only library requiring a C++17-compliant compiler. You have multiple ways to set it up:

• just include this repository as a submodule in your own git repository and use CMake add_subdirectory (or use CMake FetchContent), then link with target_link_libraries(<your-target> PUBLIC oup::oup).
• download the header and include it in your own sources.

From there, include the single header <oup/observable_unique_ptr.hpp>, and directly use the smart pointer in your own code:

#include <oup/observable_unique_ptr.hpp> #include <string> #include <iostream> #include <cassert> int main() { // Non-owning pointer that will outlive the object oup::observer_ptr<std::string> obs_ptr; { // Unique pointer that owns the object auto owner_ptr = oup::make_observable_sealed<std::string>("hello"); // Make the observer pointer point to the object obs_ptr = owner_ptr; // Observer pointer is valid assert(!obs_ptr.expired()); // It can be used like a regular raw pointer assert(obs_ptr != nullptr); std::cout << *obs_ptr << std::endl; // The unique pointer cannot be copied auto tmp_copied = owner_ptr; // error! // ... but it can be moved auto tmp_moved = std::move(owner_ptr); // OK } // The unique pointer has gone out of scope, the object is deleted, // the observer pointer is now null. assert(obs_ptr.expired()); assert(obs_ptr == nullptr); return 0; }

The following limitations are features that were not implemented simply because of lack of motivation.

• this library does not support pointers to arrays, but std::unique_ptr and std::shared_ptr both do.
• this library does not support custom allocators, but std::shared_ptr does.

In this comparison spreadsheet, the raw pointer T* is assumed to never be owning, and used only to observe an existing object (which may or may not have been deleted). The stack and heap sizes were measured with gcc 9.3.0 and libstdc++.

Labels:

• raw: T*
• unique: std::unique_ptr<T>
• weak: std::weak_ptr<T>
• shared: std::shared_ptr<T>
• observer: oup::observer_ptr<T>
• obs_unique: oup::observable_unique_ptr<T>
• obs_sealed: oup::observable_sealed_ptr<T>

Notes:

• (1) If expired() returns true, the pointer is guaranteed to remain nullptr forever, with no race condition. If expired() returns false, the pointer could still expire on the next instant, which can lead to race conditions.
• (2) By construction, only one thread can own the pointer, therefore deletion is thread-safe.
• (3) Yes if using std::atomic<std::shared_ptr<T>> and std::atomic<std::weak_ptr<T>>.
• (4) Not if using std::make_shared().
• (5) 2 by default, or 1 if using std::make_shared().

Labels are the same as in the comparison spreadsheet. The speed benchmarks were compiled with gcc 9.3.0 and libstdc++, with all optimizations turned on (except LTO), and run on a linux (5.1.0-89) machine with a Ryzen 5 2600 CPU. Speed is measured relative to std::unique_ptr<T> used as owner pointer, and T* used as observer pointer, which should be the fastest possible implementation (but obviously the one with least safety).

You can run the benchmarks yourself, they are located in tests/speed_benchmark.cpp. The benchmark executable runs tests for three object types: int, float, std::string, and std::array<int,65'536>, to simulate objects of various allocation cost. The timings below are the worst-case values measured across all object types, which should be most relevant to highlight the overhead from the pointer itself (and erases flukes from the benchmarking framework). In real life scenarios, the actual measured overhead will be substantially lower, as actual business logic is likely to dominate the time budget.

Detail of the benchmarks:

• Create owner empty: default-construct an owner pointer (to nullptr).
• Create owner: construct an owner pointer by taking ownership of an object (for oup::observer_sealed_ptr, this is using oup::make_observable_sealed()).
• Create owner factory: construct an owner pointer using std::make_* or oup::make_* factory functions.
• Dereference owner: get a reference to the underlying owned object from an owner pointer.
• Create observer empty: default-construct an observer pointer (to nullptr).
• Create observer: construct an observer pointer from an owner pointer.
• Create observer copy: construct a new observer pointer from another observer pointer.
• Dereference observer: get a reference to the underlying object from an observer pointer.

An alternative implementation of an "observable unique pointer" can be found here. It does not compile out of the box with gcc unfortunately, but it does contain more features (like creating an observer pointer from a raw this) and lacks others (their make_observable always performs two allocations). Have a look to check if this better suits your needs.