This is for entries to The Great Language Shootout.
1 Submitting guide
Now that GHC 6.6 is available, please use it! This gives us the option of using:
which should greatly improve clarity and brevity. Line count is not significant now (code is gzipped to determine size), so aim for maximum clarity.
Suggested best practices for submiting an entry to the shootout include:
- Posting the proposed code to the community to allow for a best of breed entry. Proposed code is here on the wiki and often in the haskell-cafe mailing list. This has already helped improve the submitted code.
- Provide complete performance measurements against the current best entry.
- Creating clean, functional-style code or fast, imperative-style code. There are multiple versions ("GHC", "GHC#2", "GHC#3", "GHC#4") of GHC codes on many of the benchmarks with no clear rational for the different versions. It'd be better to have entries for "GHC" be clean, short, functional code and entries for "GHC-#2" be fastest, probably-ugliest code.
- When you submit via the trac system, record in the wiki section for that entry a link to the submission.
- Check for gzip file size before you submit -- lots of points to be had there.
-- -- The Great Computer Language Shootout, http://shootout.alioth.debian.org/ -- Haskell Shootout entries, http://haskell.org/haskellwiki/Great_language_shootout -- -- Simon Marlow -- Shortened by Don Stewart --
3 Current benchmarks
The current benchmarks can highlight weak spots in libraries and compilers that need improving. Some things noticed included:
- hashtable peformance is poor. A simple binding to a basic C hashtable would be very useful
- it would be nice to have tre regexes in the core libs (instead of posix ones)