I'm not sure what you mean by "the strictness analyzer".  GHC's strictness
analyzer?
I don't know, but I would hope so since it was done already in 1980 by Alan
Mycroft.

  -- Lennart

On Sat, Feb 9, 2008 at 4:33 PM, Peter Verswyvelen <[EMAIL PROTECTED]> wrote:

> Consider the function
>
> cond x y z = if x then y else z
>
> I guess we can certainly say cond is strict in x.
>
> But what about y and z?
>
> If x is true,  then cond is strict in y
> If x is false, then cond is strict in z
>
> So we can't really say cond is lazy nor strict in its second or third
> argument.
>
> Of course, this is the case for many more functions, but in  the case of
> the if-then-else primitive, does the strictness analyzer make use of this
> "mutually exclusive strictness" fact?
>
> Cheers,
> Peter
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Haskell-Cafe mailing list
> [email protected]
> http://www.haskell.org/mailman/listinfo/haskell-cafe
>
_______________________________________________
Haskell-Cafe mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/haskell-cafe

Reply via email to