Blog

C++ Core Guidelines: More Rules about Performance

April 4, 2018

/

In this post, I continue my journey through the rules to performance in the C++ Core Guidelines. …

memoryFake

The Truth about “Raw Pointers Removed from C++”

April 2, 2018

/

Five bloggers have teamed up worldwide to deliver an April Fool's joke to readers about eliminating pointers.…

memory

No New New: Raw Pointers Removed from C++

March 26, 2018

/

Two weeks ago, the ISO C++ standard meeting took place in Jacksonville. Today I want to make a…

cheetah

C++ Core Guidelines: Rules about Performance

March 23, 2018

/

Before I write about the rules of performance, I will do a straightforward job. Accessing the elements…

RainerGrimmSmall

Which pdf bundle should I provide? Make your choice!

March 21, 2018

/

Now, it's time to choose the next pdf bundle? You will get all posts, all source files, and a cmake file…

mathematics 678969 640

C++ Core Guidelines: Rules about Statements and Arithmetic

March 16, 2018

/

Today, I will write about the remaining rules to statements and the arithmetic rules. If you don't follow…

640px Schienennetz Schweiz.svg

C++ Core Guidelines: More about Control Structures

March 9, 2018

/

My last German post C++ Core Guidelines: To Switch or not to Switch, that is the Question got…

hamlet

C++ Core Guidelines: To Switch or not to Switch, that is the Question

March 3, 2018

/

First, I have to apologize. Today, I wanted to continue my journey through the C++ Core Guidelines with…

UnderConstruction

C++ Core Guidelines: Rules for Statements

February 23, 2018

/

Before I continue with the roughly 15 rules for statements, let me finish the two rules for expressions.…

Black Forest gateau20

C++ Core Guidelines: Rules about Don’ts

February 16, 2018

/

This post is about don'ts. Here are this post's two most important rules: Don't use std::move thoughtless…

Metamorphosis frog Meyers

C++ Core Guidelines: Rules for Conversions and Casts

February 9, 2018

/

What has narrowing conversion and casts in common? They are often the source of errors; therefore, I…

dental

C++ Core Guidelines: More Rules for Expressions

February 3, 2018

/

I know this post's headline is a bit boring: More Rules for Expressions. Honestly, this post is about…

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 […]