Borrow-Checker Error Scenarios

Learn to read borrow-checker errors: they cite conflicting borrows and suggest fixes. Most resolve by shortening borrow scope, cloning at boundaries, or restructuring ownership.

Recipe

error[E0502]: cannot borrow `x` as mutable because it is also borrowed as immutable

Fix pattern: end immutable borrow before mutable borrow (narrow scope, clone, or restructure).

Working Example

Problem: holding reference while mutating container.

// Before (error)
let r = &vec[0];
vec.push(1); // invalidates r
println!("{r}");
 
// After
let first = vec[0];
vec.push(1);
println!("{first}");

Split borrows:

let (left, right) = slice.split_at_mut(mid);
// use left and right separately

What this demonstrates:

• Reallocation invalidates references (Vec::push)
• split_at_mut for two mutable regions
• Clone key at spawn boundary for async tasks

Deep Dive

Common errors: E0502 (borrow conflict), E0499 (two mut borrows), E0597 (does not live long enough). rust-analyzer often shows graph of borrows.

Gotchas

• Fighting with nested scopes - enlarge function. Fix: extract function taking &T.
• RefCell runtime borrow - panics instead of compile errors. Fix: shorten borrow_mut scope.
• Iterator holds borrow - collect or scope block ends before mutating vec.
• Struct fields overlapping - borrow whole struct. Fix: split fields into substructs.
• Async self borrow - &mut self across await. Fix: owned data in task.

Alternatives

FAQs

Related

• Lifetime Mismatch Scenarios
• Move-After-Use Scenarios
• Fighting the Borrow Checker
• Debugging Tools

Stack versions: This page was written for Rust 1.97.0 (edition 2024), Tokio 1.x, Axum 0.8, serde 1.0, sqlx 0.8, clap 4, and Polars 0.46+.