3 ms·
Co-author of that book here. Thanks for reading. :) I think overall you are at the part where Rust's documentation is at its weakest. Several people are workin
by steveklabnik 6y ago
Co-author of that book here. Thanks for reading. :)
I think overall you are at the part where Rust's documentation is at its weakest. Several people are working on more things here, but really, the basic advice I'd give you is to read and write a bunch of Rust code. The more you read, the more you'll absorb stuff like this. The more you write, the more things you'll need to figure out how to do, which will involve you looking at existing solutions, which will lead you to figure it out.
I wish I just had a second book to point you at, but alas, that doesn't really exist right now.
- poletopole 6y agoYour book was close to perfect I think in terms of learning the core language, it was very easy to read front to back. Most programming books tend to fall prey to being categorically "project" based which I hate. To be honest there were some sections that I glossed over that I should probably go back and annotate. I have to agree that finding some good github projects that are well documented to analyze would be a good start, I only wish programmers put more effort into commenting and documenting their code, ha.
- steveklabnik 6y agoThank you :) I wish so too. You should check out projects by burntsushi, alex crichton, and david tolnay. They may use advanced or complicated features that you won't need to use in most Rust code, but they all write projects that are some of my favorite in Rust. And they generally do a good job of documenting things as well. I've ordered them in a totally subjective and probably wrong "least to most likely to find magic when reading their code" order. They're all great folks and write great projects though.
- poletopole 6y agoThanks for the tip, will do.
- burntsushi 6y ago"least to most likely to find magic" Thanks. That's an amazing superlative to have. :-) Hehe.