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

This page summarizes the projects mentioned and recommended in the original post on /r/rust

Our great sponsors
  • Revelo Payroll - Free Global Payroll designed for tech teams
  • InfluxDB - Collect and Analyze Billions of Data Points in Real Time
  • SonarLint - Clean code begins in your IDE with SonarLint
  • Onboard AI - Learn any GitHub repo in 59 seconds
  • too-many-lists

    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

    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.

  • Revelo Payroll

    Free Global Payroll designed for tech teams. Building a great tech team takes more than a paycheck. Zero payroll costs, get AI-driven insights to retain best talent, and delight them with amazing local benefits. 100% free and compliant.

  • patterns

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

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

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts