Ok, thanks Gracjan!
Ben, could I ask you to pull from:
https://github.com/michalt/nofib/tree/fibon
(https://github.com/michalt/nofib.git branch `fibon`)
Or if you prefer Phab, let me know if there's some magic incantation
to make it work with this patch (`arc` currently crashes for me)
Thanks,
Thanks for the clarification!
Ryan
On Wed, Mar 22, 2017 at 9:47 AM, Ryan Scott wrote:
> I believe what Sven was saying is not that the Foldable instance for
> tuples are given "special treatment" (which is arguably an orthogonal
> discussion), but rather that
I believe what Sven was saying is not that the Foldable instance for tuples
are given "special treatment" (which is arguably an orthogonal discussion),
but rather that -XDeriveFoldable special-cases tuples, which is certainly
true.
As Edward noted, there is one possible justification for this
On Wed, Mar 22, 2017 at 4:12 AM, Sven Panne wrote:
> 2017-03-21 22:29 GMT+01:00 Edward Kmett :
>
>> [... In general I think the current behavior is the least surprising as
>> it "walks all the a's it can" and is the only definition compatible with
>>
Thanks Simon.
I made a page for it here - https://wiki.haskell.org/Inlining_and_Specialisation
Matt
On Wed, Mar 22, 2017 at 10:50 AM, Simon Peyton Jones
wrote:
> | On the same topic, I also wrote a blog post simply explaining the
> | essential things to know about the
| I didn't know the bit about INLINE being ignored on a loop-breaker
| with no warning and no way of changing the loop-breaker.
GHC tries hard NOT to choose an INLINE function as a loop breaker. But if you
write
f x = if ... then 0 else (f x')
{-# INLINE f #-}
then the only possible loop
| On the same topic, I also wrote a blog post simply explaining the
| essential things to know about the inliner and specialiser as I don't
| think they are generally appreciated. Comments welcome!
|
| http://mpickering.github.io/posts/2017-03-20-inlining-and-
| specialisation.html
2017-03-21 22:29 GMT+01:00 Edward Kmett :
> [... In general I think the current behavior is the least surprising as it
> "walks all the a's it can" and is the only definition compatible with
> further extension with Traversable. [...]
>
OTOH, the current behavior contradicts my