Boost.Capy

    • Introduction
    • Why Capy?
    • Quick Start
    • Introduction To C++20 Coroutines
      • Part I: Foundations
      • Part II: C++20 Syntax
      • Part III: Coroutine Machinery
      • Part IV: Advanced Topics
    • Introduction to Concurrency
      • Part I: Foundations
      • Part II: Synchronization
      • Part III: Advanced Primitives
      • Part IV: Communication & Patterns
    • Coroutines in Capy
      • The task Type
      • Launching Coroutines
      • Executors and Execution Contexts
      • The IoAwaitable Protocol
      • Stop Tokens and Cancellation
      • Concurrent Composition
      • Frame Allocators
    • Buffer Sequences
      • Why Concepts, Not Spans
      • Buffer Types
      • Buffer Sequences
      • System I/O Integration
      • Buffer Algorithms
      • Dynamic Buffers
    • Stream Concepts
      • Overview
      • Streams (Partial I/O)
      • Sources and Sinks (Complete I/O)
      • Buffer Sources and Sinks
      • Transfer Algorithms
      • Physical Isolation
    • Example Programs
      • Hello Task
      • Producer-Consumer
      • Buffer Composition
      • Mock Stream Testing
      • Type-Erased Echo
      • Timeout with Cancellation
      • Parallel Fetch
      • Custom Dynamic Buffer
      • Echo Server with Corosio
      • Stream Pipeline
    • Design
      • Layered Abstractions
      • Why Capy Is Separate
      • ReadStream
      • ReadSource
      • BufferSource
      • WriteStream
      • WriteSink
      • BufferSink
      • Type-Erasing Awaitables
      • AnyBufferSink
      • Executor
      • Run API
      • Why Not Cobalt?
      • Why Not Cobalt Concepts?
      • Why Not TooManyCooks?
    • Reference
  • boost::capy::strand::on_work_started
arrow_upward

boost::capy::strand::on_work_started

Notify that work has started.

Synopsis

Declared in <boost/capy/ex/strand.hpp>

void
on_work_started() const noexcept;

Description

Delegates to the inner executor's on_work_started(). This is a no‐op for most executor types.

Created with MrDocs