Hacker News Reader

Comment by sambe | Hacker News Reader

I found this to be okay as a relatively speedy intro. It's quite disorganised though - some concepts and terms appear to be assumed but then introduced properly later on. I was wondering if this was intentional or not (maybe you are supposed to be patient?).

View on HN

I assume the site is mostly aimed at people who have already read the rust book [1].

[1] https://doc.rust-lang.org/book/

Rust by Example was actually not originally a Rust team project. It was an independent work that was handed over to the Rust team for maintenance by the original author.

As I understand, it received basic polishing and updates to make sure it was correct, but hasn't been edited much beyond that.

This history is accurate. RBE is pretty low on my priority list; finishing up the book and the standard library docs are much more important right now. I to try to keep up on PRs.

Hmm, this is a bit confusing as the book is also quite terse for being a book teaching about a new language, and also heavily example based.

Not sure of the original intent, but when I started using Rust I used Rust By Example for finding snippets of things like file io where I get the gist but want to quickly see the pattern or involved parts of the stdlib.

The Rust docs are great, but having a starting point can be super welcoming so you aren't poking around blindly at different types that might be relevant.

Yeah it's more of a well-connected graph than a tree. Most of the examples that contain a concept that hasn't been covered include a link to where it is covered, and generally completely understanding the details in the example may help improve your understanding of the concept being introduced but isn't necessary to get a basic grasp.

We've had a contributor that's been slowly going through the text on a variety of things, and they're also working on untangling forward references.

Reply on news.ycombinator.com