Preparing questions and your practice workspace.
Communication, synchronization, and process lifetime
Build deterministic parallel testbench behavior by making communication, resource ownership, wakeup persistence, parentage, and cancellation explicit.
A practical guide to mailboxes, semaphores, events, fork/join variants, process trees, wait fork, disable fork, process handles, barriers, races, and shutdown.
The language bench / concurrency
fork
#5 worker();
#12 timeout();
join_any
// Parent continuationQuestion-first preparation
Practice a real question, then inspect the mechanism in its section.
One representative prompt from each major mechanism. Open any card in the live question bank.
Creates immediate children, owns their completion policy, and performs cleanup.
One process tree · four liveness obligations
Parallel syntax is only the beginning. Deterministic concurrency requires an explicit runtime tree, bounded waits, persistent progress, targeted cancellation, and cleanup.
Draw immediate children and unrelated processes.
Name the message, permit, event, or condition that releases each wait.
Preserve progress for both early and late observers.
Terminate owned work and return every held resource.
Standards and primary references
Continue preparing