Borrow two mutable values from the same HashMap

by

If you can change your datatypes and your function signature, you can use a RefCell to create interior mutability:

use std::cell::RefCell;
use std::collections::{HashMap, HashSet};

fn populate_connections(
    start: i32,
    num: i32,
    conns: &HashMap<i32, RefCell<HashSet<i32>>>,
    ancs: &mut HashSet<i32>,
) {
    let mut orig_conns = conns.get(&start).unwrap().borrow_mut();
    let pipes = conns.get(&num).unwrap().borrow();

    for pipe in pipes.iter() {
        if !ancs.contains(pipe) && !orig_conns.contains(pipe) {
            ancs.insert(*pipe);
            orig_conns.insert(*pipe);
            populate_connections(start, num, conns, ancs);
        }
    }
}

fn main() {}

Note that if start == num, the thread will panic because this is an attempt to have both mutable and immutable access to the same HashSet.

Safe alternatives to RefCell

Depending on your exact data and code needs, you can also use types like Cell or one of the atomics. These have lower memory overhead than a RefCell and only a small effect on codegen.

In multithreaded cases, you may wish to use a Mutex or RwLock.

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. Double mutable borrow error in a loop happens even with NLL on
  11. How to return a reference to a sub-value of a value that is under a mutex?
  12. How do I return an instance of a trait from a method?
  13. “borrowed value does not live long enough” seems to blame the wrong thing
  14. Is it possible to make a type only movable and not copyable?
  15. How to use struct self in member method closure
  16. How do I call a function through a member variable?
  17. Why are Rust executables so huge?
  18. How do you pass a Rust function as a parameter?
  19. How do I implement a trait with a generic method?
  20. How do I use conditional compilation with `cfg` and Cargo?
  21. When I can use either Cell or RefCell, which should I choose?
  22. Return an async function from a function in Rust
  23. How to implement `serde::Serialize` for a boxed trait object?
  24. How do I disambiguate traits in Rust?
  25. How do I change a function’s qualifiers via conditional compilation?
  26. Use of undeclared type or module `std` when used in a separate module
  27. How do I cope with lazy iterators?
  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