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.
Learning Rust With Entirely Too Many Linked Lists helps you to solidify your understanding of what ownership and borrowing means for implementing data structures.
Rust Design Patterns aims to be Rust's analogue to the Gang of Four book for Java.
Rust API Guidelines provides a "checklist and elaboration"-style reference for how to design interfaces that are idiomatic.
After The Rust Programming Language ("The Book" that everyone else is referring to) and cargo clippy (check out the lint reference for more lints that are allowed by default but which also have explanations for why you might want to disallow them), check out these free online books:
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
- Coming from Python. Can anyone offer some generic tips and answer a few questions?
- I’m curious