I personally feel that we should take @brson's initial proposal and move forward with that, stabilizing
std::test (I'd be ok eliding
black_box, it often isn't unnecessary due to how the closure works).
I agree with @nikomatsakis that the high-order bit here is that the benchmarking support we stabilize needs to feel built-in. That means you shouldn't have to edit
Cargo.toml or add
extern crate annotations to get it working. Even reaching for
Bencher is a great stretch over how
I've got lots of reservations about what
Bencher actually does, but the interface is so minimal today that I think we can easily stabilize it and then enhance it over time with more bells and whistles in a backwards-compatible way.
I should also emphasize that replacing the
test crate with your own is super unstable. This relies on the exact interface that libtest in-tree has today as the compiler will generate structures that libtest has. If you're relying on
--extern test=... shadowing the built-in test crate I would consider that a bug in the compiler that we didn't properly gate it and I would also want to reserve the right to break it. The precise structures in libtest change over time, and there's no reason they should be defacto stable.