[Haskell-cafe] Categorized Weaknesses from the State of Haskell 2011 Survey

Evan Laforge qdunkan at gmail.com
Wed Sep 14 02:02:26 CEST 2011


I would appreciate is a few paragraphs in the toplevel haddock page or
module that describe the general architecture and layout of the
modules, as well as the typical entry points.  Since the module system
doesn't have a notion of private modules and it's common to re-export
symbols, it can be unclear where to start, which modules to look at,
and why it is the author chose that particular decomposition for the
functions.  Overall design and architecture is hard to get out of the
code.

I think the same goes for each module.  It's frustrating when I want
to figure out how something works, and each module just has a giant
chunk of license copy-paste at the top.



More information about the Haskell-Cafe mailing list