Archive for category: Blog

Cooperative Interruption of a Thread in C++20: Callbacks

July 15, 2024

I introduced in my last post "Cooperative Interruption of a Thread in C++20" callbacks. Today, I dive…

TimelineCpp20Interruption

Cooperative Interruption of a Thread in C++20

July 1, 2024

/

A typical question in my C++ seminars is: Can a thread be killed? Before C++20, my answer is no. With…

Chrono: Input

June 24, 2024

You can also apply the format specifier for formatted input. This post is the eleventh in my…

Chrono I/O: Unformatted and Formatted

June 17, 2024

Chrono I/O consists of reading and writing chrono types. The various chrono types support unformatted…

Chrono I/O

May 20, 2024

Chrono I/O consists of reading and writing chrono types. The various chrono types support unformatted…

Time Zones: Online Classes

May 13, 2024

Today, I will continue to present the functionality of the time zones of the C++20 chrono extension. This…

TimelineCpp20CoreLanguage

Time Zones: Details

May 6, 2024

/

Today, I present the time-zones functionality of the C++20 extension. This post is the seventh…

C++20: Query Calendar Dates and Ordinal Dates

April 22, 2024

The extended chrono library makes it relatively easy to ask for the time duration between calendar dates. This…

C++20: Displaying and Checking Calendar Dates

April 15, 2024

I created calendar dates in my last post, "C++20: Creating Calendar Dates," and I will display and check…

C++20: Creating Calendar Dates

April 8, 2024

In this post, I will dive deeper into calendar dates and create them. If this post is too overwhelming…

Latest news

std::execution: More SendersDecember 23, 2024 - 10:40 am
std::execution offers three types of senders: factories, adapters, and consumers. I’ll take a closer look at these today. Most of the following content is from proposal P2300R10. I will try to represent it more concisely. Sender Factory A sender factory is an algorithm that takes no senders as parameters and returns a sender. I already […]
std::execution: SenderDecember 16, 2024 - 11:25 am
std::execution offers three types of senders: factories, adapters, and consumers. I’ll take a closer look at these today. Most of the following content is from proposal P2300R10. I will try to represent it more concisely. Sender Factory A sender factory is an algorithm that takes no senders as parameters and returns a sender. execution::schedule execution::sender […]
std::execution: Composition of SendersDecember 9, 2024 - 10:25 am
Most sender adaptors are composable using the pipe operator. Let me start with a simple example of composition with the pipe operator. Instead of the nested function calls call1(call2(input)) you can write call1 | call2(input) or even: input | call1 | call2 Function composition Okay, this example was straightforward. Let’s do something more complicated. Proposal […]
std::execution: Inclusive ScanDecember 2, 2024 - 10:30 am
Inclusive scan solves problems related to range queries, such as calculating the sum of a range of elements in an array. It is also used in range minimum queries and various other algorithms. Before I present the asynchronous inclusive scan, I introduce the inclusive scan, aka prefix sum. Prefix Sum In computer science, the prefix […]
std::execution: Asynchronous AlgorithmsNovember 25, 2024 - 9:06 am
std::execution supports many asynchronous algorithms for various workflows. Presenting proposal P2300R10 is not easy. First, it is very powerful, and second, it is very long. Therefore, I concentrate on specific aspects of the proposal. What are the priorities of this proposal? Priorities The terms execution resource, execution agent, and scheduler are essential for the understanding […]
std::executionNovember 18, 2024 - 9:03 am
std::execution, previously known as executors or Senders/Receivers, provides “a Standard C++ framework for managing asynchronous execution on generic execution resources“. (P2300R10) Side Note Change of plans. My original plan was to present the C++26 library after the core language. However, the implementation status of the library is not good enough. Therefore, I decided to continue […]