Archive for category: Blog

async

Asynchronous Function Calls

May 26, 2016

/

std:.async feels like an asynchronous function call. Under the hood std::async is a task. One, which…

tasksEng

Tasks

May 21, 2016

/

Tasks were one of the latest additions to the C++11 standard. They give you a better abstraction than…

conditionVariable

Condition Variables

May 17, 2016

/

Condition variables allow us to synchronize threads via notifications. So, you can implement workflows…

threadLocal

Thread-Local Data

May 16, 2016

/

By using the keyword thread_local, you define the thread local data. Thread-local can easily be…

callOnce

Thread-Safe Initialization of Data

May 15, 2016

/

The story is simple if the data is not modified when shared between threads. The data has only to be…

deadlockResolved

Prefer Locks to Mutexes

May 12, 2016

/

If the previous post showed something, it's that you should use mutexes with great care. That's why you…

Deadlock

The Risks of Mutexes

May 10, 2016

/

The usage of mutexes seems extremely simple. There is a critical section in the code that a single thread…

readerWriterLocks

Reader-Writer Locks

May 7, 2016

/

With C++14 came reader-writer locks. The idea is straightforward and promising. Arbitrary reading threads…

bossWorker

Source Code Repository

May 5, 2016

/

I created a repository for the source code. It's on GitHub and has the name ModernesCppSource:https://github.com/RainerGrimm/ModernesCppSource.git This…

bossWorker

Threads Sharing Data

April 30, 2016

/

One of the biggest challenges of thread management begins when the threads share non-const data Data…

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