Hal Daume III <[EMAIL PROTECTED]> writes: [snip my functions that use the ST monad to do (//)]
> You shouldn't try to write these functions. You should do all array > modifications within the ST monad, rather than looking for a pure > solution. All right, but why? It seems an obvious trick, take some pieces that benefit from imperative processing, and wrap them in ST, leaving the rest of the program as it were. Can you (or anybody else) explain the memory behaviour I see (using hundreds of megabytes, but only tens of K visible in the profiling output)? -kzm -- If I haven't seen further, it is by standing in the footprints of giants _______________________________________________ Haskell-Cafe mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/haskell-cafe
