Blog

TimelineCpp20Libraries

C++20: The Library

October 28, 2019

/

My last post "C++20: The Core Language" presented the new features of the C++20 core language. Today,…

TimelineCpp20Core

C++ 20: The Core Language

October 27, 2019

/

My last post C++20: The Big Four started with an overview of concepts, ranges, coroutines, and modules.…

TimelineCpp20BigFourUpdate

C++20: The Big Four

October 23, 2019

/

This post presents you the big four: concepts, ranges, coroutines, and modules. C++20 has a lot…

RainerGrimmSmall

The new pdf bundle is ready: C++ Core Guidelines: Performance

October 23, 2019

/

I have prepared the pdf bundle. To get it is quite simple. If you subscribe to the newsletter, you…

TimelineCpp

The Next Big Thing: C++20

October 17, 2019

/

C++20 will be the next big C++ standard after C++11. As C++11 did, C++20 will change the way we program…

ConcurrencyCoverFrame

“Concurrency with Modern C++” has a new chapter

October 15, 2019

/

I'm happy to announce. I added a new chapter to lock-based concurrent data structures…

mistake 968334 1280

C++ Core Guidelines: Naming and Layout Rules

October 10, 2019

/

The C++ core guidelines have about twenty naming and layout rules. A few of them are obvious; a few of…

cemetery

C++ Core Guidelines: Lifetime Safety And Checking the Rules

October 1, 2019

/

The lifetime safety profile in the C++ core guidelines boils down to one issue: don't dereference a possible…

industrsy

C++ Core Guidelines: Bounds Safety

September 26, 2019

/

Today's post concerns the second C++ Core Guidelines: Bounds Safety profile. The goal of the profile…

abseiling 1842180 1280

C++ Core Guidelines: Type Safety by Design

September 18, 2019

/

What does that mean: type safety by design. Type safety by design just means that you always initialize…

checklist 1295319 1280

C++ Core Guidelines: Type Safety

September 8, 2019

/

The C++ core guidelines support three profiles: type safety, bounds safety, and lifetime safety. Thanks…

checklist 911840 1280

C++ Core Guidelines: Profiles

September 6, 2019

/

Informally, profiles are a subset of rules of the C++ core guidelines for specific concerns such as type…

Latest news

Hazard Pointers in C++26May 5, 2025 - 11:12 am
Hazard pointers provide garbage collection in C++ and solve the ABA problem. First of all. What is a hazard pointer? Proposal P2530R3 gives a nice explanation: A hazard pointer is a single-writer multi-reader pointer that can be owned by at most one thread at any time. Only the owner of the hazard pointer can set […]
A Lock-Free Stack: A Hazard Pointer Implementation Explained IIApril 7, 2025 - 11:11 am
In my last post, I started to explain a hazard pointer implementation: A Lock-Free Stack: A Hazard Pointer Implementation Explained I. Today, I will continue to explain the implementation. The Retire List The retire list has the public member functions isInUse, addNode, and deleteUnusedNodes. Additionally, it has the inner class RetireNode, an atomic member of […]
A Lock-Free Stack: A Hazard Pointer Implementation Explained IMarch 24, 2025 - 11:37 am
In my last post, I presented a hazard pointer implementation: A Lock-Free Stack: A Hazard Pointer Implementation. Today, I will explain the implementation. MyNode is a class template, parametrized by the type it holds: data. MyNode models the concept Node. template <typename T> concept Node = requires(T a) { {T::data}; { *a.next } -> std::same_as<T&>; […]
A Lock-Free Stack: A Hazard Pointer ImplementationMarch 10, 2025 - 11:42 am
Hazard Pointers solve all issues of the previous implementation: A Lock-Free Stack: A Simple Garbage Collector. From one Week to two Weeks You may have already noticed. I will change my blog publishing frequency from one to two weeks in the future. Writing a post using your voice is exceptionally exhausting and time-consuming. Hazard Pointers […]
A Lock-Free Stack: A Simple Garbage CollectorFebruary 24, 2025 - 11:58 am
My next lock-free stack includes a simple garbage collector. I discussed the concurrent execution of more than one topAndPush call is a Race Condition. I can safely delete a node if not more than one topAndPush call is executing concurrently. This observation is crucial for solving this memory leak issue: I store removed nodes on […]
A Lock-Free Stack: Atomic Smart PointerFebruary 17, 2025 - 11:47 am
The easiest way to solve this memory leak issue from the last post is to use a std::shared_ptr. Atomic Smart Pointer There are two ways to apply atomic operations on a std::shared_ptr: In C++11, you can use the free atomic functions on std::shared_ptr. With C++20, you can use atomic smart pointers. C++11 Using atomic operations […]