ppend
> Rule fired: foldr/app
> Rule fired: unpack-list
> Rule fired: foldr/app
> Rule fired: unpack-list
> Rule fired: unpack-list
> Rule fired: unpack-list
> bash-3.1$
>
> | -Original Message-
> | From: Simon Meier [mailto:iridc...@gmail.com]
> | Sent: 14 June
om: Simon Meier [mailto:iridc...@gmail.com]
| Sent: 14 June 2011 16:48
| To: Simon Peyton-Jones
| Cc: cvs-ghc@haskell.org
| Subject: Re: Debugging non-firing rewrite rules
|
| Hi Simon,
|
| the attached module illustrates the problem. I don't think it's a compiler
bug. Its more
|
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
o 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 2011 14:44
| To: cvs-ghc@haskell.org
| Subject: Debugging
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
