And the Winners are:
Last week, I launched a quiz. The price was it to win one of the five vouchers for the book “The Modern C++ Programming Cookbook” 2en Edition by Marius Bancila.
This author has not written his bio yet.
But we are proud to say that Rainer Grimm contributed 702 entries already.
Last week, I launched a quiz. The price was it to win one of the five vouchers for the book “The Modern C++ Programming Cookbook” 2en Edition by Marius Bancila.
I give away five vouchers for my book “C++20”. In return, I have a question about the Big Four: concepts, ranges, coroutines, and modules. Which feature excites your most and why?
After the introduction to std::atomic_flag in my last post, Synchronization with Atomics in C++20, I want to dive deeper. Today, I created a ping-pong game using condition variables, std::atomic_flag and std::atomic<bool>. Let’s play.
I’m proud to present the early release of my book to C++20 on LeanPub. The book is 50 % done and has more than 300 pages and 150 code examples of content. I will update the book at least two times in 2021. Of course, you will get each update of the book.
Sender/receiver workflows are pretty common for threads. In such a workflow, the receiver is waiting for the sender’s notification before it continues to work. There are various ways to implement these workflows. With C++11, you can use condition variables or promise/future pairs; with C++20, you can use atomics.
Atomics receives a few essential extensions in C++20. Today, I start with the new data type std::atomic_ref.
I’m looking for proofreaders for my new book “C++20”. The book serves two purposes. It provides you the details of the new C++20 standard and shows you how to use it. This book includes more than one hundred fifty examples to study the theory in praxis.
This post concludes my presentation of library features in C++20. Today I am writing about the class std::source_location and a few functions for bit manipulation.
When your program’s compilation broke with a brand-new C++20 feature, you often end with a few questions: Did I do something wrong? Did I find a compiler bug? Does my compiler not yet support this feature? Thanks to the feature testing in C++20, the last question is easy to answer.
When you compare signed and unsigned integers, you may not get the result you expect. Thanks to the six std::cmp_* functions, there is a cure in C++20.
