Hey folks. I’m wondering about the status of
#[bench]. This is the feature that is preventing me from migrating to stable rust, since benchmarks are a development workflow–my code needs to be fast, and I run
cargo bench a lot to find out if I’m fast yet or not. As a consequence I have to keep nightly on the development machines.
The stabilization metabug says the API has “known problems” and that we “want more pluggable framework”, but what that means in practice, I have no idea.
- What is the problem exactly with the existing API?
- Is there a shovel-ready solution to solve that problem floating around somewhere?
- How will we recognize a solution to this problem if we see it?
- Who owns this feature? Is it unowned?
One other tidbit I’ve dug up in my research–this feature was discussed in March but the conclusion of that discussion seems to be “punting” and “we should probably make a FAQ about this”. It does seem to be punted on, but if there’s a FAQ, I can’t dig it up.
Since this is the last mile to get to stable Rust, I’m at least somewhat motivated to make a go at it, if I can wrap my head around the problem and the parameters for an acceptable solution.