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

1. too-many-lists

   1 222 3,353 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. InfluxDB

   influxdata.com featured

   InfluxDB high-performance time series database. Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.

   

3. book

   2 654 15,958 9.7 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 65 8,342 6.2 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