Memory leak because of missing Drop implementation.

[cafce25]

Currently when a Map gets dropped it does not clean up any of it's keys or values i.e. the following tests fail:

#[test]
fn drops_keys() {
    use std::rc::Rc;
    let mut m: Map<Rc<()>, (), 8> = Map::new();
    let k = Rc::new(());
    m.insert(Rc::clone(&k), ());
    drop(m);
    assert_eq!(Rc::strong_count(&k), 1);
}

#[test]
fn drops_values() {
    use std::rc::Rc;
    let mut m: Map<(), Rc<()>, 8> = Map::new();
    let v = Rc::new(());
    m.insert((), Rc::clone(&v));
    drop(m);
    assert_eq!(Rc::strong_count(&v), 1);
}

[yegor256]

@cafce25 many thanks! How would you recommend implementing it? I'm trying this, but doesn't help:

impl<K: Clone + PartialEq, V: Clone, const N: usize> Drop for Map<K, V, N> {
    fn drop(&mut self) {
        for (k, v) in self.iter() {
            drop(k);
            drop(v);
        }
    }
}

[yegor256]

@cafce25 I added the tests: 4fb2bb0

[cafce25]

Probably some combination of iteration over self.pairs and MabeUninit::assume_init_drop() or add and use a IntoIterator implementation of Map should work.

[yegor256]

@cafce25 once again, thanks! Both of your tests work: 93f5097

[yegor256]

@rultor release, tag is 0.0.10

[rultor]

@rultor release, tag is 0.0.10

@yegor256 OK, I will release it now. Please check the progress here

[rultor]

@rultor release, tag is 0.0.10

@yegor256 Done! FYI, the full log is here (took me 3min)