std.benchmark ready for review. Manager sought after

Somedude lovelydear at mailmetrash.com
Mon Apr 9 09:44:44 PDT 2012


Le 09/04/2012 17:23, Francois Chabot a écrit :
> Why is there so much emphasis on printBenchmarks()?
> 
> benchmark() and runBenchmarks() are clearly the core of this library,
> and yet they are relegated to second-class citizen: "Oh, I guess you can
> use this". Normally, I wouldn't be so picky, but this is a standard
> library. Focus should be on functionality.
> 
> Providing formatted output is a nice bonus, but to me, it's just a
> bonus. Any benchmarking part of a large project is bound to format the
> output itself (to log benchmark results against revisions in a database
> or something like that).
> 
> Also, benchmark() and runBenchmarks() are kind of confusing at first
> glance. Something along the lines of benchmarkModule() and
> benchmarkAllModules() would be more sensible.

The printBenchmark facility is cool and should be included imho.
It helps benchmarking being as standard as unit testing.
We don't want to have to write again and again the same boilerplate code
for such trivial uses.


More information about the Digitalmars-d mailing list