Ways to Handle Non-blocking Returns in Message-passing Programs...
summary
Compares a concrete purchase-by-reply example against eight ways to handle non-blocking returns, showing actual code shapes from message-passing plumbing and void RPCs through callbacks, lambdas, futures, code builders, fibers, and co_await. Claims a “Holy Grail” linear form with explicit reentry markers is the readability baseline, then measures verbosity, hidden state-change points, and whether the approach supports snapshot serialization. Concludes futures or object-callbacks are pragmatic today, while co_await is closest to ideal but still problematic for reliable serialization.
AI-written summary · about
chapters (4)
related talks
30mCONQUERING CONCURRENCY WITH FUNCTIONAL PROGRAMMING
01h 35mThinking Outside the Synchronisation Quadrant
47mYou Keep Using That Word
54mDesigning for Concurrency Using Message Passing in C++
01h 16mConcurrency Approaches: Past, Present, and Future
29mComparative Asynchronous Programming
20mSubprocesses, Threads and Fibers
01h 16mC++ Feature Coroutines, Beginner Friendly