Concurrency & Channels Lab

Simulate actor-style message passing over mpsc channels, backpressure in bounded queues, and thread-safe data synchronization without data races.

Multi-Threaded Channels (mpsc) & Mutex Simulator

Visualize thread message passing without shared memory, and RAII MutexGuard locking.

Channel & Mutex Operations

mpsc Channel:

Mutex<State> Lock Contention:

Ownership Transfer in Channels:

When tx.send(val) is invoked, full ownership of val moves across thread boundaries. The sending thread can no longer read or modify it.

Thread Pipeline & Channel Ring Bufferstd::sync::mpsc

FIFO Buffer (2 pending)Producers → Queue → Consumer

Job #1 Payload

Job #2 Payload

Mutex Guard Status UNLOCKED (Ready)

No thread currently holds the lock. Ready for instant acquisition.

The Send Trait (Move Across Threads)

Indicates that ownership of the data can be safely transferred to another OS thread. If a type does not contain thread-bound handles (like raw pointers or Rc), Rust auto-implements Send.

The Sync Trait (Shared References Across Threads)

Indicates that immutable references (&T) can be read concurrently from multiple threads without data races. Mathematically: T: Sync <=> &T: Send.

Loading RustViz Engine...