# Pre-RFC: Stabilize \`#\[bench\]\`, \`Bencher\` and \`black\_box\`

**URL:** <https://internals.rust-lang.org/t/pre-rfc-stabilize-bench-bencher-and-black-box/4565>\
**Category:** language design\
**Created:** [January 5, 2017, 9:54pm UTC](https://internals.rust-lang.org/t/pre-rfc-stabilize-bench-bencher-and-black-box/4565 "2017-01-05T21:54:18Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![brson](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/brson/32/5197_2.png) [@brson](https://internals.rust-lang.org/u/brson)\
**Post date:** [January 6, 2017, 1:21am UTC](https://internals.rust-lang.org/t/pre-rfc-stabilize-bench-bencher-and-black-box/4565/9 "2017-01-06T01:21:14Z")

</div>

> [@SimonSapin](#):
>
> But rustc-tests can also be used with #[test] and #[bench] to run benchmarks on stable Rust today.

Woah `#[bench]` is _stable_? And rustc can be convinced to use an _alternate_ test crate? How do you do that? That could change my opinions about the solution space considerably.

My concern with the alternate proposals so far is that they take us back to the drawing board. We _are_ going back to the drawing board to design custom test frameworks, and relatively soon, but anything involving design must take considerably longer than essentially rubber stamping a de-facto solution.

---

_[View the full topic](https://internals.rust-lang.org/t/pre-rfc-stabilize-bench-bencher-and-black-box/4565)._