Chapter 16.2: Possibly Unnecessary Analogy
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 18.3k
- Forks
- 4.1k
- Avg merge
- 14m
- Merged PRs (30d)
- 1
Description
- I have searched open and closed issues and pull requests for duplicates, using these search terms:
- channel
- duck
- analogy
- I have checked the latest
mainbranch to see if this has already been fixed, in this file:
URL to the section(s) of the book with this problem:
https://doc.rust-lang.org/book/ch16-02-message-passing.html
Description of the problem:
Sending information via a communication channel is something I believe most people would be able understand well even without an analogy. While I found the analogy of a rubber duck floating down the river quite adorable, in my opinion, it lengthens the introduction unnecessarily. Though, this is not a big issue, obviously, maybe even a bit nitpicky of me.
Suggested fix:
Reword and shorten paragraphs 3 and 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open src/ch16-02-message-passing.md around lines 16–25 and compare it with the rendered Chapter 16.2 section. Review paragraphs 3 and 4 for the rubber-duck analogy, then reword and shorten them while preserving the introduction’s explanation of channels. Done means the introduction is more concise and the updated wording remains clear in the rendered book.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100