Proposal: Add a benchmark section to .cabal files
aslatter at gmail.com
Tue Oct 4 20:06:27 CEST 2011
On Tue, Oct 4, 2011 at 12:49 PM, Johan Tibell <johan.tibell at gmail.com> wrote:
> On Tue, Oct 4, 2011 at 7:57 AM, Duncan Coutts <duncan.coutts at googlemail.com>
>> In general, yes I think benchmarking is a sensible follow-on from test
>> suites. We can follow the same approach of specifying a protocol so that
>> we can add more sophisticated interfaces later as we gain experience wit
> What do you think about the very basic interface I gave? It basically just
> makes it possible to create executables that are distinguishable as
> benchmarks. That seems like a very small step but it solves more or less all
> of my problems*.
> Should I go ahead and implement it?
> * I prefer not to use the workaround as having spurious executables confuses
> Hackage (which lists them) and users.
I've had decent luck with adding a benchmark as a 'test' section,
which puts the executable in a predictable place.
> cabal-devel mailing list
> cabal-devel at haskell.org
More information about the cabal-devel