Re: [Haskell-cafe] Problems with strictness analysis?

"Patai Gergely" writes:

My only problem is that if I try to write a program without thinking about performance first and not bothering with annotations as long as "it works", I end up with something that's practically impossible to profile as the costs spread everywhere.

I didn't think that was the case, does that happen with the example you posted? (I find GHC's heap profiling to be useful in tracking down these "strictness leaks".) -k -- If I haven't seen further, it is by standing in the footprints of giants