On Tue, Aug 02, 2011 at 07:41:29AM +, Simon Peyton-Jones wrote:
>
> * Ian: make the code in integer-simple use simpler pattern matching. Ian,
> done?
Done!
Thanks
Ian
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/l
Simon
| -Original Message-
| From: Simon Marlow [mailto:marlo...@gmail.com]
| Sent: 01 August 2011 15:29
| To: Simon Peyton-Jones
| Cc: Max Bolingbroke; cvs-ghc@haskell.org; Malcolm Wallace; Chris Dornan
| Subject: Re: integer-simple
|
| On 01/08/2011 14:15, Simon Peyton-Jones wrote:
| >
69.html
Cheers,
Simon
Simon
| -Original Message-
| From: omega.th...@gmail.com [mailto:omega.th...@gmail.com] On Behalf Of Max
| Bolingbroke
| Sent: 01 August 2011 08:55
| To: Simon Peyton-Jones
| Cc: Malcolm Wallace; Chris Dornan; cvs-ghc@haskell.org
| Subject: Re:
ris Dornan; cvs-ghc@haskell.org
| Subject: Re: integer-simple
|
| On 1 August 2011 08:09, Simon Peyton-Jones wrote:
| > I'm guessing here, but I bet I know what's going on. If integer-simple
uses
| > inexhaustive pattern matching, GHC will generate calls to 'patError
On 1 August 2011 08:54, Max Bolingbroke wrote:
> They seem to originate from using bang patterns in the definitions:
I just checked and the bangs are irrelevant. It's just a general
behaviour of the pattern match desugarer where it generates code for
situations it could potentially see are imposs
On 1 August 2011 08:09, Simon Peyton-Jones wrote:
> I’m guessing here, but I bet I know what’s going on. If integer-simple uses
> inexhaustive pattern matching, GHC will generate calls to ‘patError’ for the
> missing cases. That in turn generates a dependency on base, which is where
> patError is
