Rust: error[E0505]: cannot move out of `s` because it is borrowed
You moved a value while a reference to it was still in use.
error[E0505]: cannot move out of `s` because it is borrowedcannot move out of because it is borrowedE0505 move out of value occurs here borrow later used heremove out of `x` occurs here borrow of `x` occurs here Meaning
A reference (&s) must not outlive a move of s. Use the reference before moving, clone (s.clone()), borrow instead of moving (takes(&s)), or restructure ownership so the borrow ends first.
Common causes
- Passing
sby value while&sis later used - Moving into a thread/closure while borrowed
- Returning a value while keeping a reference
- Pushing into a collection while holding a ref
- Struct fields borrowed then moved
⚡ Quick fix
- Pass a reference (
&s) or clone - Finish using the borrow before the move
- Use
Rc/Arcfor shared ownership
Detailed fix by platform
Rust
let r = &s; println!("{r}"); drop(s); // borrow ends before the move
How to diagnose
- Borrow — Still used after the move?
- Fix — Clone/borrow/reorder?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Blocking waiting for file lock on package cache / build directory Cargo: Blocking waiting for file lock on package cache / on build directory
- cargo: failed to get from registry (spurious network error) Cargo: warning: spurious network error (2 tries remaining): [35] SSL connect error / error: failed to download from `https://index.crates.io/...`
- E0373: closure may outlive the current function Rust: error[E0373]: closure may outlive the current function, but it borrows `v`, which is owned by the current function
Most viewed in Rust
- E0308 Rust: error[E0308]: mismatched types — expected `X`, found `Y`
- E0502 Rust: error[E0502]: cannot borrow `x` as mutable because it is also borrowed as immutable
- feature edition2024 is required / Cargo.lock version too new Cargo: error: failed to parse manifest — feature `edition2024` is required / lock file version 4 requires `-Znext-lockfile-bump`
Other ways to find it
Where this error sits
Origin: Application & API. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026