Why can I iterate over a slice twice, but not a vector?

by

Like you said, for works by taking the thing you asked it to iterate over, and passing it through IntoIterator::into_iter to produce the actual iterator value. Also as you said, into_iter takes the subject by value.

So, when you try to iterate over a Vector directly, this means you pass the entire vector, by value, into its IntoIterator implementation, thus consuming the vector in the process. Which is why you can’t iterate over a vector directly twice: iterating over it the first time consumes it, after which it no longer exists.

However, slices are different: a slice is an immutable, borrowed pointer to its data; immutable, borrowed pointers can be copied freely. This means that the IntoIterator for immutable slices just borrows the data and doesn’t consume it (not that it could). Or, to look at it another way, its IntoIterator implementation is simply taking a copy of the slice, whereas you can’t copy a Vec.

It should be noted that you can iterate over a Vec without consuming it by iterating over a borrow. If you check the documentation for Vec, you’ll note that it lists implementations of IntoIterator for Vec<T>, &Vec<T> and &mut Vec<T>.

let mut a: Vec<i32> = vec![1, 2, 3];

for i in &a {           // iterate immutably
    let i: &i32 = i;    // elements are immutable pointers
    println!("{}", i);
}

for i in &mut a {       // iterate mutably
    let i: &mut i32 = i;// elements are mutable pointers
    *i *= 2;
}

for i in a {            // iterate by-value
    let i: i32 = i;     // elements are values
    println!("{}", i);
}

// `a` no longer exists; it was consumed by the previous loop.

More Related Contents:

  1. Return local String as a slice (&str)
  2. How can I swap in a new value for a field in a mutable reference to a structure?
  3. How to get a reference to a concrete type from a trait object?
  4. How do I return a reference to something inside a RefCell without breaking encapsulation?
  5. Conditionally iterate over one of several possible iterators
  6. Is there any way to create a type alias for multiple traits?
  7. How to convert a String into a &’static str
  8. What’s an idiomatic way to print an iterator separated by spaces in Rust?
  9. Double mutable borrow error in a loop happens even with NLL on
  10. What are move semantics in Rust?
  11. println! error: expected a literal / format argument must be a string literal
  12. How to return a reference to a sub-value of a value that is under a mutex?
  13. How do I return an instance of a trait from a method?
  14. “borrowed value does not live long enough” seems to blame the wrong thing
  15. Weird behaviour when using read_line in a loop
  16. How can this instance seemingly outlive its own parameter lifetime?
  17. Why are Rust executables so huge?
  18. What do I have to do to solve a “use of moved value” error?
  19. Why does removing return give me an error: expected type `()` but found type
  20. Linking the lifetimes of self and a reference in method
  21. Is there a way to create a function pointer to a method in Rust?
  22. Return an async function from a function in Rust
  23. Borrow two mutable values from the same HashMap
  24. Is there any difference between matching on a reference to a pattern or a dereferenced value?
  25. What is an auto trait in Rust?
  26. Creating a vector of zeros for a specific size
  27. What is the difference between immutable and const variables in Rust?
  28. How do I create a HashMap with type erased keys?
  29. How to print structs and arrays?
  30. Can Rust optimise away the bit-wise copy during move of an object someday?

Leave a Comment