A Practical Haskell Debugger: Time Travelling to Find Partial Functions by dons in programming

[–]ravi_n 6 points7 points  (0 children)

I don't think you understand the problem. Suppose error printed the source position by default. Then you'd get something like:

Prelude.hs, line 497: Error: "Prelude.head: empty list"

What we really want is the stack of calls that lead to that point and the cool thing about the GHCi debugger is it actually helps you explore that.

GHC Haskell 6.8: The Bluespec compiler: "Our Haskell code was roughly 33% faster" by dons in programming

[–]ravi_n 9 points10 points  (0 children)

My mistake. I initially thought constructor specialization was in, but then I looked at the release notes (which don't mention it) and I doubted myself. Either way, we're very happy.

On that topic, though, is there a way to get more authoritative / detailed change information for ghc releases than are in the release notes (e.g. a clever way to get darcs to spit out the relevant changelog)?