Is there an elegant solution to modifying a structure while iterating?

by

You cannot modify the structure you are iterating over, that is, the vector points. However, modifying the elements that you get from the iterator is completely unproblematic, you just have to opt into mutability:

for i in points.iter_mut() {

Or, with more modern syntax:

for i in &mut points {

Mutability is opt-in because iterating mutably further restricts what you can do with points while iterating. Since mutable aliasing (i.e. two or more pointers to the same memory, at least one of which is &mut) is prohibited, you can’t even read from points while the iter_mut() iterator is around.

More Related Contents:

  1. How do I create a heterogeneous collection of objects?
  2. The compiler suggests I add a ‘static lifetime because the parameter type may not live long enough, but I don’t think that’s what I want
  3. Is it possible to control the size of an array using the type parameter of a generic?
  4. Are polymorphic variables allowed?
  5. Does println! borrow or own the variable?
  6. How do I pass disjoint slices from a vector to different threads?
  7. Why is it possible to implement Read on an immutable reference to File?
  8. Compare enums only by variant, not value
  9. How can I call a mutating method while holding a reference to self?
  10. How do you actually use dynamically sized types in Rust?
  11. Why do I need rebinding/shadowing when I can have mutable variable binding?
  12. How can I put an async function into a map in Rust?
  13. How to operate on 2 mutable slices of a Rust array?
  14. Mutating one field while iterating over another immutable field
  15. How can I use a module from outside the src folder in a binary project, such as for integration tests or benchmarks?
  16. How to match on data type in Rust?
  17. Why does Rust allow mutation through a reference field using an immutable binding?
  18. Multiple return types from a method
  19. How to end a borrow in a match or if let expression?
  20. How do I synchronously return a value calculated in an asynchronous Future?
  21. Why does this mutable borrow live beyond its scope?
  22. Why does creating a mutable reference to a dereferenced mutable reference work?
  23. Cannot borrow `x` as mutable more than once at a time
  24. Removing elements from a Vec based on some condition [duplicate]
  25. What’s the difference between using the return statement and omitting the semicolon in Rust?
  26. How to idiomatically alias a crate in Rust 2018?
  27. Cannot borrow immutable borrowed content as mutable
  28. Can a struct containing a raw pointer implement Send and be FFI safe?
  29. Lazy sequence generation in Rust
  30. Is there a way to get the field names of a struct in a macro?

Leave a Comment