Nicolas Bigaouette

It is always a good idea to run code/tests through valgrind. One could simply run the current tests (without docs) through valgrind, and add more that use yet uncovered code...

Note that jemalloc _removed_ valgrind support (see https://github.com/jemalloc/jemalloc/commit/9a8add1510456464bc496320990ec234798bd381) but this does not seems to be included in rust's version of a jemalloc. Rust uses jemalloc @ 33184bf69813087bf1885b0993685f9d03320c69 plus a couple...

Great read, thanks. Maybe an optional combination `alloc_system`+nightly+valgrind could be added. As @adamcrume mentioned in #66, it might not be a good idea to depend on `alloc_system` and nightly for...

So I've experimented running the tests through valgrind, but it's not as trivial as it looks. First, as mentioned above, using jemalloc (the default memory allocator in rust) will confuse...