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

1. too-many-lists

   1 227 3,455 2.6 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.

2. Stream

   getstream.io featured

   Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.

   

3. book

   2 663 17,076 9.5 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.

4. patterns

   3 66 8,637 3.8 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