nonblockinghashmap

nonblockinghashmap copied to clipboard

Leaks and double frees in unsafe code

3

Multiple occurrences of leaks and (possible) double frees caused by unmatched `Box::into_raw` and `Box::from_raw` calls have be identified in current implementation. see https://github.com/rlei/nonblockinghashmap/commit/6e6793b0787e633db891738c36e86fcfd059dca0 for an (incomplete) list of leaks.

rlei

is there any API to remove an entry?

1

I just see `put` and `get`, at least we need a `remove` API.

Xudong-Huang