Jeff Smits

Ideally `cargo bench` would output info of all the runs that it does, then we can do this as well as use more rigorous statistics (#4). Sadly I don't currently...

That is _very_ interesting. I didn't know that was possible. I want to look into that then, but not sure when I'll have time. I'll try to at least look...

I just ran `kcov` locally, because I was curious and the unit (quickcheck) tests give a 93.3% coverage :smile: I also tried to get coverage from the integration tests but...

Yeah, I'm not going to look into it. Can you set up the badge? I would do it for you but it's inconvenient to get this working of my fork...

Yeah, I don't like the dependency on gnuplot either. But at least there are [windows binaries for gnuplot](http://gnuplot.info/download.html). The reason I even came up with was because I needed an...

Ok, so more info on the current implementation. I pushed the working code, so you can try out [this branch](https://github.com/Apanatshka/cargo-benchcmp/tree/plot). Usage: ``` Compares Rust micro-benchmark results. Usage: cargo benchcmp table...

Cool, then I'll use the `rustc-hash` crate I guess :) Perhaps this is something to add to the crate README?

I think the best way to go about this is to have a user-wide `~/.elm/package-cache/` that has a copy of any new package you download, and just have soft-links to...

@mgold that's another issue, one that I'd like to address separately. (You can simply record the hash of the commit instead of the tag when the new version is published)

Both of these make sense to me. I can see myself using `lazy_static::lazy!`. I never really care about the `ref`, all I did was copy-paste an example and adapt it.