rust/book
1
0
Fork 0
mirror of https://github.com/rust-lang/book.git synced 2026-09-15 00:49:13 -04:00
Code Issues Packages Projects Releases Wiki Activity

grumble mumble ordered list bug

Browse Source
This commit is contained in:
Carol (Nichols || Goulding)
2017-10-30 11:13:19 -04:00
parent 7db393dae7
commit d4879ff7fc
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
second-edition/src/ch16-02-message-passing.md
View File

@@ -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.
<!-- NEXT PARAGRAPH WRAPPED WEIRD INTENTIONALLY SEE #199 -->
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`.
<!-- above -- can you give us a general idea of what that means for us in this
program? -->