change of strictness in zipWith

[David Feuer]

It was done intentionally, to avoid having the zipWith semantics depend on
which, if either, of the venerable foldr2 RULES fired. But I'd personally
be very happy to just nix the shady rule (the other is fine), and accept
the performance penalty.
On Jan 2, 2015 5:24 AM, "Henning Thielemann" <lemming at henning-thielemann.de>
wrote:

>
> On Fri, 2 Jan 2015, Roman Cheplyaka wrote:
>
>  I don't think it does. The first pattern (a:as) will be refuted, and the
>> second (b:bs) won't try to match at all.
>>
>
> right - stupid me
>
> Then, the new behavior of zipWith is really a bug. I added a ticket:
>
> https://ghc.haskell.org/trac/ghc/ticket/9949
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://www.haskell.org/mailman/listinfo/libraries
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/libraries/attachments/20150102/19692f19/attachment.html>