Join GitHub today
mapAccum and mapAccumM should be strict in their state #218
referenced this issue
Aug 4, 2015
I made this change because it seemed like the right thing to do. I've just spent two hours tracking down a Hoogle space leak that was only exhibiting on some machines (specifically the real Hoogle server) and not others (my development machine). Turned out to be entirely down to a not-strict accumulator which due to the old version of conduit was causing issues. Just shows that accumulators should definitely be strict!