Returning iterator of a Vec in a RefCell

by

You cannot do this because it would allow you to circumvent runtime checks for uniqueness violations.

RefCell provides you a way to “defer” mutability exclusiveness checks to runtime, in exchange allowing mutation of the data it holds inside through shared references. This is done using RAII guards: you can obtain a guard object using a shared reference to RefCell, and then access the data inside RefCell using this guard object:

&'a RefCell<T>        -> Ref<'a, T> (with borrow) or RefMut<'a, T> (with borrow_mut)
&'b Ref<'a, T>        -> &'b T
&'b mut RefMut<'a, T> -> &'b mut T

The key point here is that 'b is different from 'a, which allows one to obtain &mut T references without having a &mut reference to the RefCell. However, these references will be linked to the guard instead and can’t live longer than the guard. This is done intentionally: Ref and RefMut destructors toggle various flags inside their RefCell to force mutability checks and to force borrow() and borrow_mut() panic if these checks fail.

The simplest thing you can do is to return a wrapper around Ref, a reference to which would implement IntoIterator:

use std::cell::Ref;

struct VecRefWrapper<'a, T: 'a> {
    r: Ref<'a, Vec<T>>
}

impl<'a, 'b: 'a, T: 'a> IntoIterator for &'b VecRefWrapper<'a, T> {
    type IntoIter = Iter<'a, T>;
    type Item = &'a T;

    fn into_iter(self) -> Iter<'a, T> {
        self.r.iter()
    }
}

(try it on playground)

You can’t implement IntoIterator for VecRefWrapper directly because then the internal Ref will be consumed by into_iter(), giving you essentially the same situation you’re in now.

More Related Contents:

  1. How do I write an iterator that returns references to itself?
  2. How to implement Iterator and IntoIterator for a simple struct?
  3. How can I add new methods to Iterator?
  4. Are there equivalents to slice::chunks/windows for iterators to loop over pairs, triplets etc?
  5. Iterator returning items by reference, lifetime issue
  6. Iterating over a slice’s values instead of references in Rust?
  7. is it possible to filter on a vector in-place?
  8. How do I perform iterator computations over iterators of Results without collecting to a temporary vector?
  9. How can I zip more than two iterators?
  10. Writing a generic function that takes an iterable container as parameter in Rust
  11. Why can’t I store a value and a reference to that value in the same struct?
  12. Is there any way to return a reference to a variable created in a function?
  13. What are non-lexical lifetimes?
  14. 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
  15. Lifetime error when creating a function that returns a value implementing serde::Deserialize
  16. How do I write the lifetimes for references in a type constraint when one of them is a local reference?
  17. When is it useful to define multiple lifetimes in a struct?
  18. Lifetime troubles sharing references between threads
  19. Moved variable still borrowing after calling `drop`?
  20. How do I specify lifetime parameters in an associated type?
  21. How does the lifetime work on constant strings / string literals?
  22. What is the difference between ‘&self’ and ‘&’a self’?
  23. How to operate on 2 mutable slices of a Rust array?
  24. When returning the outcome of consuming a StdinLock, why was the borrow to stdin retained?
  25. Sharing a struct with trait objects as properties across threads
  26. Thread references require static lifetime?
  27. Why does Rust disallow mutable aliasing?
  28. Using max_by_key on a vector of floats [duplicate]
  29. How do I cope with lazy iterators?
  30. Rust lifetime error expected concrete lifetime but found bound lifetime

Leave a Comment