Man, that @rustlang book is immensely frustrating. Lots of "You can use X (which we won't go over until many chapters later)"
Introducing concepts that you don't explain just muddies the waters and confuses the learner.
-
-
Replying to @rossipedia @rustlang
sorry to hear that. It's a tricky balance since Rust concepts work together.
1 reply 0 retweets 2 likes -
I mean, overall it's a great piece of work, there's just a handful of frustrating bits where concepts are mentioned with the assumption the reader knows what it is.
2 replies 0 retweets 0 likes -
Replying to @rossipedia @jntrnr
We worked *really* hard to minimize forward references; like, dozens of hours. We agree it’s not great but as
@jntrnr says it’s impossible to fully remove them :(1 reply 0 retweets 1 like -
That's immensely appreciated effort, truly. It happens to be frustrating on my part, as this is now my 3rd attempt at following along the book, sequentially, and these things stop me dead in my tracks :(
2 replies 0 retweets 0 likes -
Even though I'm nowhere near a newbie (20+ years exp programming, several in the C/C++ space). Although it definitely could be a fault with me... I really want to dig into Rust, but I may end up having to just build something and cut my teeth on the compiler errors...
1 reply 0 retweets 1 like -
Replying to @rossipedia @jntrnr
Out of interest, which refs are causing the most issues?
1 reply 0 retweets 0 likes -
Does the book have a GH repo? I'd be happy to open an issue/submit a PR. I'd feel better being proactive about fixing rather than just venting on Twitter
1 reply 0 retweets 1 like
Yes! rust-lang/book
Issues are better than PRs for this kind of thing. Let’s talk! I appreciate it 
-
-
0 replies 0 retweets 4 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.