If you use Rust only occasionally and do not want to spend days reading tons of documents, then the topic can be for you. I'm creating a document covering major aspects of Rust you need to keep in mind to create a quality Rust code. You can share your thought here helping me to make the document better.
Sorry, I don't understand it. Should your guide be a replacement for e.g. reading the official book? Or more a reminder for people who have learned Rust some years ago, and now need something to remember the details? The second might make sense, I think it is sometimes called cheat-sheet? For this there are dozen in the Internet, rust-by-example or the rust-cookbook are variants of this, the Google Android paper is also similar. As a replacement for the official book? I think the stuff of that book is really the minimal content each Rust programmer would need, but perhaps it could be presented in a bit more compact form. But we even have that, what I discovered a bit too late: The Rust Book (Abridged) | The rs Book
PS: I still wonder about the hundreds Rust books at Amazon. Might most of them be fully AI generated garbage? For Nim, we actually got more than a dozen books at Amazon in the last two years, having only two in all the years before. Some might have been so bad that even Amazon removed them fast from the shop.
[EDIT]
OK, because of the title of this thread (people using the search tool), I should mention also the following document, even I have some doubt that it is useful. But well, they have a few dozen of GitHub stars:
No, this guide isn't a replacement. It is more like LLM model for humans. How does AI work? It reads all Rust books, all 1000 ones. But it doesn't store the books in the original form. It strips the books in certain patterns it used after to answer your questions about Rust programming. But LLM creator do not publish their model in a human readable form. I'm trying to do so.
I also checked your books. No, it's exactly what I want to avoid. Second book is simply bad because it has examples with errors. My brain works in the way it memorizes code but it doesn't memorize comment saying - this code isn't compilable because such and such things are not allowed in Rust.
I think I should add a small paragraph about iterators. What do you think?
Please note that these are not my books. My own Rust book is https://rust-for-c-programmers.com/
For the two mentioned books above, I have read non of them. But my impression was that The Rust Book (Abridged) | The rs Book is not bad, if I had known it earlier, I might have started learning Rust with that. And Introduction - Fast Track to Rust is just much too thin, with nearly no real content.
For your creation, I have still some problem to understand the purpose and use case. I will bookmark it and watch your progress.