Re: Debugging non-firing rewrite rules

2011-06-15 Thread Simon Meier
e fired: Class op showsPrec > Rule fired: map > Rule fired: fold/build > Rule fired: Class op >> > Rule fired: Class op show > Rule fired: Class op return > Rule fired: unpack-list > Rule fired: unpack-append > Rule fired: unpack-append > Rule fired: unpack-a

Re: Debugging non-firing rewrite rules

2011-06-14 Thread Simon Meier
ns we can add it to the > regression suite (if there is a bug) to ensure it doesn't happen again. > > Simon > > | -Original Message- > | From: cvs-ghc-boun...@haskell.org [mailto:cvs-ghc-boun...@haskell.org] On > Behalf Of > | Simon Meier > | Sent: 11 June 201

Debugging non-firing rewrite rules

2011-06-11 Thread Simon Meier
Hi, there's quite some material on how to debug/track rewrite rules that do fire. However, I couldn't find information about how to find out what is wrong with a rule that supposedly should, but actually doesn't fire. Concretely, I would like to add a rewrite rule that converts mconcat . map (f