Later, I bought "Programming Rust" by Jim Blandy, and it changed everything.
This is one of the books which I will gladly buy once more when it is updated.
Agreed, Programming Rust is really nice and I read a dozen of Rust books already. I'll be buying 2nd edition as soon as it's available.
also, i am not saying The book is any good beyond a tour of the language. come to think of it, it's actually less like TC++PL or D&EC++, and more like the tour of c++.
> it's just really a translation of c++ patterns into rust equivalences. no explanation, history
Perhaps. I came from a strong C++ background, maybe that's crucial when reading it. It all just made perfect sense to me.
For example, in the git2 crate there is both:
https://docs.rs/git2/0.13.12/git2/struct.Branch.html
and
https://docs.rs/git2/0.13.12/git2/struct.Branches.html
Where Branches implements Iterator.
I think it's documented under something like "How to implement Iterator" but if that's not where people will go looking when they need it, then it should be somewhere else.
Here's a quote that really resonated with my early experience with the language:
I find, even today, it's impossible to check documentation or read "the book", alone, and produce idiomatic rust code. Finally one breaks down and asks on Stack Overflow or one of chat or forum outlets and receives an answer which (almost always accidentally) comes across as, "Oh, didn't you know it?? We always express those ideas in this format here [example code]". I've come to accept and appreciate this way. But it can be baffling and off-putting to newbies who wonder how they should have known.