There are at least two reasons why this is disallowed:
You would need to have two concurrent mutable references to map
— one held by the iterator used in the for
loop and one in the variable map
to call map.remove
.
You have references to the key and the value within the map when trying to mutate the map. If you were allowed to modify the map in any way, these references could be invalidated, opening the door for memory unsafety.
A core Rust principle is Aliasing XOR Mutability. You can have multiple immutable references to a value or you can have a single mutable reference to it.
I didn't think moving/borrowing applied to references.
Every type is subject to Rust's rules of moving as well as mutable aliasing. Please let us know what part of the documentation says it isn't so we can address that.
Why it is trying to move a reference?
This is combined of two parts:
- You can only have a single mutable reference, so mutable references don't implement the
Copy
trait
for
loops take the value to iterate over by value
When you call for (k, v) in map {}
, the ownership of map
is transferred to the for loop and is now gone.
I'd perform an immutable borrow of the map (&*map
) and iterate over that. At the end, I'd clear the whole thing:
fn do_it(map: &mut HashMap<String, String>) {
for (key, value) in &*map {
println!("{} / {}", key, value);
}
map.clear();
}
remove every value with a key that starts with the letter "A"
I'd use HashMap::retain
:
fn do_it(map: &mut HashMap<String, String>) {
map.retain(|key, value| {
println!("{} / {}", key, value);
!key.starts_with("a")
})
}
This guarantees that key
and value
no longer exist when the map is actually modified, thus any borrow that they would have had is now gone.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…