From d4879ff7fccefc41734fcf39b8b514bfc1b29633 Mon Sep 17 00:00:00 2001 From: "Carol (Nichols || Goulding)" Date: Mon, 30 Oct 2017 11:13:19 -0400 Subject: [PATCH] grumble mumble ordered list bug --- second-edition/src/ch16-02-message-passing.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/second-edition/src/ch16-02-message-passing.md b/second-edition/src/ch16-02-message-passing.md index b1212ff65..d631d9ab5 100644 --- a/second-edition/src/ch16-02-message-passing.md +++ b/second-edition/src/ch16-02-message-passing.md @@ -58,14 +58,16 @@ river: everything sent down any of the streams will end up in one river at the end. We’re going to start with a single producer for now, but we’ll add multiple producers once we get this example working. + + The `mpsc::channel` function returns a tuple, the first element of which is the sending end and the second element the receiving end. The abbreviations `tx` and `rx` are traditionally used in many fields for *transmitter* and *receiver* respectively, so we give our variables those names to indicate each end. We’re using a `let` statement with a pattern that destructures the tuples; we’ll be -discussing the use of patterns in `let` statements and destructuring in Chapter -18. Using a `let` statement in this way is a convenient way to extract the -pieces of the tuple returned by `mpsc::channel`. +discussing the use of patterns in `let` statements and destructuring in +Chapter 18. Using a `let` statement in this way is a convenient way to extract +the pieces of the tuple returned by `mpsc::channel`.