-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thoughts on Patterns #115
Labels
Milestone
Comments
That's possible. In general, we've been trying to fight the "x and advanced x" ... well, pattern, in chapters. Hrm. |
Yeah, it's not ideal. I guess TLDR, my feeling is that we don't want people to feel like they need to get through all of this material on their way to other things -- it's slick, but not essential. So whatever way we can find to make sure readers don't get blocked on it. |
carols10cents
added a commit
that referenced
this issue
Jul 2, 2016
I feel like these are useful for the same reasons, are very similar, and should therefore be discussed in quick succession. Connects to #115.
carols10cents
added a commit
that referenced
this issue
Jul 2, 2016
carols10cents
added a commit
that referenced
this issue
Jul 2, 2016
I feel like destructuring tuples and struct fields is less common. I do think it's worth pointing out that _ doesn't bind, though. Connects to #115.
carols10cents
added a commit
that referenced
this issue
Jul 2, 2016
Fixes #115. Thanks to some brainstorming with @pindell-matt and @selfup at Turing, we've got what I think is a better analogy of a coin sorting machine!
AbrarNitk
pushed a commit
to FifthTry/rust-book
that referenced
this issue
Jun 2, 2021
Fix: ch19-03 - Add missing caption id for Listing 19-21
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As it currently stands, the Patterns section feels like it has a quite different style from the rest of the book. It feels much more "Comprehensive Reference" rather than "Friendly guide to the most vital things for a new Rustacean to learn."
We should think carefully about the most important details about patterns that people need to know at this juncture, and consider moving the rest of this content to a later "Advanced patterns" section (which we can work out a good place for).
Alternatively, we had discussed having an explicit marker for "advanced" sections you can skip on a first read, and perhaps we could mark this one that way?
The text was updated successfully, but these errors were encountered: