Re: Debugging non-firing rewrite rules

2011-06-15 Thread Simon Meier
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

RE: Debugging non-firing rewrite rules

2011-06-15 Thread Simon Peyton-Jones
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 |

Re: Debugging non-firing rewrite rules

2011-06-14 Thread Simon Meier
Hi Simon, the attached module illustrates the problem. I don't think it's a compiler bug. Its more that I don't understand the foldr/build fusion framework currently in use well-enough. Anyways, I'm very glad for any help. best regards, Simon 2011/6/13 Simon Peyton-Jones : > Any chance you could

RE: Debugging non-firing rewrite rules

2011-06-13 Thread Simon Peyton-Jones
Any chance you could make a standalone example demonstrating the problem? ie one or two modules with suitable definitions, perhaps some stubs. ({-# NOINLINE #-} is useful for the stubs.) Not only does that make it easier to identify what's going wrong, but it also means we can add it to the re