Re: [Haskell-cafe] runStateT execution times measurement baffling

On Saturday 22 October 2011, 13:55:36, Bas van Dijk wrote:

On 20 October 2011 22:16, thomas burt wrote:

...

Perhaps I will try and force `stuffToDo` not to leave any partially evaluated thunks behind.... and compare the cost then.

What happens when you switch to a strict StateT?

He already uses the strict StateT:

By the way I'm using ghc-6.10.4 and Control.Monad.Trans.State.Strict.

We need to see more of the code to find out what's going on.