I likewise agree this isn't a job for Hoogle, but on a related note see my previous post in here about needing better documentation (specifically a proper manual for most hackage pages, not just a bare bones API doc): http://www.haskell.org/pipermail/haskell-cafe/2009-October/067969.html
-R. Kyle Murphy -- Curiosity was framed, Ignorance killed the cat. On Mon, Oct 26, 2009 at 10:11, David Leimbach <[email protected]> wrote: > On 10/26/09, David Virebayre > <[email protected]<dav.vire%[email protected]>> > wrote: > > On Sun, Oct 25, 2009 at 2:09 PM, Curt Sampson <[email protected] > > > > wrote: > >> But zaxis, here's another thing to look at. There's usually a "view > >> source" link beside most of the functions that come up in the Haddock > >> documentation to which Hoogle links. It's worth clicking. You would be > >> surprised (certainly I was!) at how often looking at the definition > >> of a function suddenly makes it quite clear what it does, when the > >> description didn't quite do it for you. (This is one of the joys of > >> Haskell.) > > > > I tried that with parsec 3, my brain exploded :) > > _______ > > or the printf implementation. I tried to figure it out, then the > Cenobites came and got me. > > > ________________________________________ > > Haskell-Cafe mailing list > > [email protected] > > http://www.haskell.org/mailman/listinfo/haskell-cafe > > > _______________________________________________ > Haskell-Cafe mailing list > [email protected] > http://www.haskell.org/mailman/listinfo/haskell-cafe >
_______________________________________________ Haskell-Cafe mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell-cafe
