Threading, Tasks, Channels and Timers

Native threading, synchronization, cancellation, tasks, continuations, channels and timer behavior.

4 physical componentsSource 6d429559

Targets in this family

Component	Kind	Production dependencies	Representative header
`Threading`	static	`Core.Base`, `TimeZone`	`System/AsyncCallback.hpp`
`Threading.Tasks`	static	`Core.Base`, `Threading`	`System/IAsyncDisposable.hpp`
`Threading.Channels`	interface	`Core.Base`, `Threading.Tasks`	`System/Threading/Channels/BoundedChannelFullMode.hpp`
`Timers`	static	`ComponentModel`, `Core.Base`, `Threading (private)`	`System/Timers/ElapsedEventArgs.hpp`

Threading

Threading covers threads, synchronization primitives, cancellation and thread-pool-oriented behavior using native C++ synchronization. Object lifetime and callback capture remain the caller’s responsibility.

Tasks

Threading.Tasks provides Task, ValueTask-shaped and continuation APIs for porting familiar control flow. It does not add C# language async/await to C++ and is not a CLR task scheduler.

Channels

Threading.Channels is a header-only component layered over tasks for bounded/unbounded channel patterns. Cancellation, completion and blocking behavior should be designed explicitly in native code.

Timers

Timers owns elapsed-event timer behavior and privately depends on Threading. A timer callback can outlive the initiating scope unless ownership and shutdown are coordinated.

Callback lifetime

A continuation, event or timer that captures a raw object pointer can become unsafe after destruction. Prefer an explicit owner, cancellation and join/teardown protocol.

Complete catalogue

See all 41 physical components for external dependencies, ownership and direct graph details.