Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
I agreeing with the others that The Book, but to answer your question:
However, when I decided to make the jump from Python to Rust for better compile-time guarantees, I read the original first edition of The Book and then followed it up with Learning Rust With Entirely Too Many Linked Lists to solidify my understanding of what ownership and borrowing mean for actually writing more complex code.
While it wasn't around back then, I'd recommend The Little Book of Rust Books for finding more to read following that. (eg. The Rust Performance Book, Rust Design Patterns, and Rust API Guidelines)
While it wasn't around back then, I'd recommend The Little Book of Rust Books for finding more to read following that. (eg. The Rust Performance Book, Rust Design Patterns, and Rust API Guidelines)
Related posts
- I've been writing C# for nearly a decade, but I want to learn how to build programs with Rust. What do I need to change about how I structure my code?
- Is there a coding style and set of best-practices that avoid (not bypass) "fighting the borrow checker"?
- Looking for advices for and from experienced developer
- Any recommend resources to start learning?
- Coming from Python. Can anyone offer some generic tips and answer a few questions?