Luca Barbato

Probably would be good to start discussing with upstream cargo about supporting `debug=split` and/or override the profiles.

In general `cargo test --all-features` is the best way to have surprising results and it should be actively avoided. The most common problem is when you have mutually exclusive features...

a workaround landed libav already http://git.libav.org/?p=libav.git;a=commit;h=f7de52354fe15ba7cae141b44ffdd01e560f0e47

https://gist.github.com/1074654 possible fixes from a friend of mine

The example was wrong ``` rust trait Trait { type Associated; } struct A { f: F } ``` Sorry.

It does not miss it but I would need to find either the `sys::TypePath` or even `sys::Type` and not just `sys::Ident`. My use-case is https://docs.rs/derive_bounded/latest/derive_bounded/ An extended example ``` rust...

@ericholscher since there is no activity I'd move it.

Since we use `getrusage()` the maximum resident set would come for free though: ``` rust rusage.ru_maxrss ``` I can try to bake a patch if adding this would be acceptable.

> It's not that easy. > > * We do not run the benchmarked process directly, but through a shell. `rusuage` would probably show the memory usage of both the...

https://github.com/edubkendo/atom-racer/pull/79 this is the current kludge that works well enough to me.