Part 18. Concurrency and Async

A thread is a separate path of execution inside one program.

10 items

Section	Title
1	Threads in Zig
2	Mutexes
3	Atomics
4	Condition Variables
5	Async Functions
6	Await and Suspension
7	Event Loops
8	Channels and Queues
9	Data Races
10	High Performance Concurrent Design

Writes › Book › Zig › Part 18. Concurrency and Async ›

Threads in Zig

A thread is a separate path of execution inside one program.

Writes › Book › Zig › Part 18. Concurrency and Async ›

Mutexes

A mutex is a lock for shared data.

Writes › Book › Zig › Part 18. Concurrency and Async ›

Atomics

An atomic operation is a small operation that can safely happen while several threads are running.

Writes › Book › Zig › Part 18. Concurrency and Async ›

Condition Variables

A condition variable lets one thread sleep until another thread says that something has changed.

Writes › Book › Zig › Part 18. Concurrency and Async ›

Async Functions

Async code lets a program start an operation now and receive the result later.

Writes › Book › Zig › Part 18. Concurrency and Async ›

Await and Suspension

await means: wait until an asynchronous operation has finished, then continue with its result.

Writes › Book › Zig › Part 18. Concurrency and Async ›

Event Loops

An event loop is code that waits for events, then runs the right piece of work for each event.

Writes › Book › Zig › Part 18. Concurrency and Async ›

Channels and Queues

A queue is a data structure for passing work from one part of a program to another.

Writes › Book › Zig › Part 18. Concurrency and Async ›

Data Races

A data race happens when two threads access the same memory at the same time, at least one access writes, and there is no proper synchronization.

Writes › Book › Zig › Part 18. Concurrency and Async ›

High Performance Concurrent Design

High performance concurrent design means using several threads or tasks without making the program slower, more fragile, or harder to reason about.