Borrow pointer errors recursively traversing tree [duplicate]

by

This seems to be a weakness of the borrow checker, and is perhaps a bug. The problem is that you are borrowing at in the match and then modifying it. Unfortunately, the compiler doesn’t see that the at inside the loop and outside the loop are conceptually different. We can make them explicitly different, however:

enum AVLTree {
    Tree(Box<AVLTree>),
    Empty,
}

impl AVLTree {
    fn insert_element(&mut self) {
        let mut at = self;
        loop {
            let tmp_at = at; // Main change
            match tmp_at {
                &mut AVLTree::Tree(ref mut left) => {
                    at = &mut **left;
                }
                &mut AVLTree::Empty => unreachable!()
            }
        }
    }
}

fn main() {}

Here, we transfer the mutable borrow from at to tmp_at, then transfer it to left, then transfer it back to at.

A prettier option may be to use a new scope:

fn insert_element(&mut self) {
    let mut at = self;
    loop {
        match {at} { // Main change
            &mut AVLTree::Tree(ref mut left) => {
                at = &mut **left;
            }
            &mut AVLTree::Empty => unreachable!(),
        }
    }
}

More Related Contents:

  1. What is the difference between iter and into_iter?
  2. How does for syntax differ from a regular lifetime bound?
  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. Why is this match pattern unreachable when using non-literal patterns?
  7. Is there any way to create a type alias for multiple traits?
  8. What’s an idiomatic way to print an iterator separated by spaces in Rust?
  9. Proper way to return a new string in Rust
  10. How do I return an instance of a trait from a method?
  11. “borrowed value does not live long enough” seems to blame the wrong thing
  12. Is it possible to make a type only movable and not copyable?
  13. How to use struct self in member method closure
  14. How do I call a function through a member variable?
  15. Why are Rust executables so huge?
  16. How do you pass a Rust function as a parameter?
  17. How do I implement a trait with a generic method?
  18. How do I use conditional compilation with `cfg` and Cargo?
  19. When I can use either Cell or RefCell, which should I choose?
  20. Return an async function from a function in Rust
  21. How to implement `serde::Serialize` for a boxed trait object?
  22. Can I take a byte array and deserialize it into a struct?
  23. How do I create a Rust callback function to pass to a FFI function?
  24. Why does a lazy-static value claim to not implement a trait that it clearly implements?
  25. How do I convert a usize to a u32 using TryFrom?
  26. What is the purpose of the unit type in Rust?
  27. Why does the Rust compiler request I constrain a generic type parameter’s lifetime (error E0309)?
  28. Cannot pass self as callback parameter due to double borrowing
  29. How do I create a HashMap with type erased keys?
  30. How to print structs and arrays?

Leave a Comment