Message passing concepts in Rust - Step-by-Step Execution

Concept Flow - Message passing concepts

Create Channel

↓

Sender sends message

↓

Message in Channel Buffer

↓

Receiver receives message

↓

Process message

↓

Repeat or Close Channel

Message passing in Rust uses channels where a sender sends messages to a receiver through a buffer, enabling safe communication between threads.

Execution Sample

Rust

use std::sync::mpsc;
fn main() {
    let (tx, rx) = mpsc::channel();
    tx.send(42).unwrap();
    let val = rx.recv().unwrap();
    println!("Received: {}", val);
}

This code creates a channel, sends the number 42 from sender to receiver, then prints the received value.

Execution Table

Step	Action	Channel State	Sender State	Receiver State	Output
1	Create channel	Empty buffer	Sender ready	Receiver ready
2	Sender sends 42	Buffer contains 42	Sender ready	Receiver ready
3	Receiver calls recv()	Buffer empty after recv	Sender ready	Receiver received 42
4	Print received value	Buffer empty	Sender ready	Receiver received 42	Received: 42
5	End of example	Buffer empty	Sender ready	Receiver received 42	Program ends

💡 Program ends after message is received and printed.

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
tx (Sender)	Created	Ready to send	Ready to send	Ready
rx (Receiver)	Created	Ready to receive	Received 42	Received 42
Channel Buffer	Empty	Contains 42	Empty	Empty
val	None	None	42	42

Key Moments - 3 Insights

Why does the receiver block at recv() until a message arrives?

Because recv() waits for a message to be available in the channel buffer, as shown in step 3 of the execution_table where the receiver waits and then receives 42.

What happens if the sender sends multiple messages before the receiver calls recv()?

Messages accumulate in the channel buffer until the receiver calls recv(), similar to step 2 where the buffer holds the message until received.

Can the sender send messages after the receiver has dropped?

No, sending will fail because the channel is closed when the receiver is dropped, which would cause send() to return an error (not shown in this simple example).

Visual Quiz - 3 Questions

Look at the execution_table at step 2, what is the state of the channel buffer?

A Empty

B Contains 42

C Contains multiple messages

D Closed

💡 Hint

Check the 'Channel State' column at step 2 in the execution_table.

At which step does the receiver actually get the message?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look at the 'Receiver State' column to see when it changes to 'Received 42'.

If the sender sends two messages before the receiver calls recv(), how would the channel buffer state change at step 2?

A Buffer would be empty

B Buffer would contain one message

C Buffer would contain two messages

D Buffer would be closed

💡 Hint

Recall that messages accumulate in the buffer until received, as explained in key_moments.

Concept Snapshot

Message passing in Rust uses channels with a sender and receiver.
Sender sends messages into a buffer.
Receiver waits and receives messages from the buffer.
recv() blocks until a message is available.
Channels enable safe communication between threads.

Full Transcript

This example shows how Rust's message passing works using channels. First, a channel is created with a sender and receiver. The sender sends the number 42 into the channel buffer. The receiver waits at recv() until the message arrives, then receives it. Finally, the program prints the received value. The channel buffer holds messages until the receiver takes them. This mechanism allows threads to communicate safely by passing messages instead of sharing memory directly.