Is there a coding style and set of best-practices that avoid (not bypass) "fighting the borrow checker"?

• too-many-lists

  219 3,014 0.0 Rust

  Learn Rust by writing Entirely Too Many linked lists

  

Also, once you've worked through something like The Book, give Learning Rust With Entirely Too Many Linked Lists a read. It really helped me to understand what ownership and borrowing mean for implementing data structures.

• book

  626 14,211 6.9 Rust

  The Rust Programming Language

  

Also, once you've worked through something like The Book, give Learning Rust With Entirely Too Many Linked Lists a read. It really helped me to understand what ownership and borrowing mean for implementing data structures.

• WorkOS

  workos.com sponsored

  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.

  

• patterns

  63 7,665 7.6 Handlebars

  A catalogue of Rust design patterns, anti-patterns and idioms

  

Well, there's https://rust-unofficial.github.io/patterns/ for a start.

Suggest a related project