I may have overstated Don's point. I didn't mean that it was no longer a problem with the language - I was saying that this was an effective way to eliminate the problem within a given program.

Space leaks are certainly a huge problem with the language. For novice/casual users the runtime is effectively a black box and space leaks are a showstopper. Don was pointing out that if your process involves using these tools routinely (such as at Galois) then the problem diminishes greatly.

Yours, Thomas.

On 23/09/11 16:10, Paul A. Steckler wrote:

On Fri, Sep 23, 2011 at 2:58 PM, Thomas Sewell Thomas.Sewell@nicta.com.au wrote:

...

On a related note, Don Stewart gave a talk about his experience in Haskell working at Galois recently, and pointed out that profiling by types in their runtime effectively eliminated their problems with the famous Haskell space-leak issue.

Do you mean, they now have a good idea where to stuff seq's in their code?

Still a bother to have to routinely run the memory profiler on your code.

-- Paul