A good resource for learning ownership, borrowing, references and all that jazz: <a href="https://rust-unofficial.github.io/too-many-lists/" rel="nofollow noreferrer">https://rust-unofficial.github.io/too-many-lists/</a>
I found that the oriely book "Programming in Rust" to be very thorough and helpful for me. It helped me really understand the concepts of Rust. Although the free rust documentation is fantastic too!<p><a href="https://www.oreilly.com/library/view/programming-rust-2nd/9781492052586/" rel="nofollow noreferrer">https://www.oreilly.com/library/view/programming-rust-2nd/97...</a>
Read the Rust Book. Rust is not like other languages, you need to understand the fundamentals before staring a project, otherwise you will get frustrated.
I have found ChatGPT to be most useful as a way of explaining tricky code examples in Rust.<p>So while going through Rust by Example, I'll paste programs into ChatGPT and have a conversation with it about how specific pieces work. I've also done LeetCode problems and then asked ChatGPT for feedback about my approach.
Edited for grammar and format
Read the 'Rust Book' as others suggested. Make small programs.<p>- Result and Option ( if let, match etc)<p>- understand references / mutable references<p>- ownership and borrowing.<p>- traits.<p>- learn generics<p>- Box, RC, Refcell,<p>- threads with Arc/ Mutexes.<p>- std::sync - channels(tx, rx)<p>- tokio (if you want to get better at an async runtime)<p>- take up an open source project and do it rust
Thanks!
I am looking at The Book (<a href="https://doc.rust-lang.org/book/" rel="nofollow noreferrer">https://doc.rust-lang.org/book/</a>), but hoped there was an amazing person on youtube.<p>Yeah, I'll build something, finally trying webassembly.
Create a Rust program that writes a PPM file to stdout of a shape you want to draw.<p>Ask ChatGPT to give you example programs you need to implement based on part of rust you want to learn.
First, quickly go through all the documentation. Then start writing whatever comes to mind. And if you don't understand something, go back to the documentation. For me, that's the best way to learn.