patch applied (cabal): "Describe benchmark sections in the user guide"

Conrad Parker conrad at
Tue Oct 25 04:09:34 CEST 2011

(I wish this project was in git so I could just reply to the patch inline ;-)

Regarding this comment in the docs:

+For brevity, the example package
+does not include a library or any normal executables, but a real package would
+be required to have at least one library or executable.

is there a technical reason for requiring that the package contain
some other library or executable? It seems like it would be useful to
allow benchmark-only packages that eg. provide a benchmark of some
task that ties together two other library packages (st. the benchmark
wouldn't naturally fit into either of those packages), or shootout
submissions etc.


On 25 October 2011 08:59, Johan Tibell <johan.tibell at> wrote:
> Wed Oct 19 08:32:33 PDT 2011  Johan Tibell <johan.tibell at>
>  * Describe benchmark sections in the user guide
>    M ./Cabal/doc/developing-packages.markdown +69
> View patch online:
> _______________________________________________
> cabal-devel mailing list
> cabal-devel at

More information about the cabal-devel mailing list