Simon Marlow wrote:
The point is, GHC has no such thing as the overall program memory
limit unless by that you mean the total amount of memory + swap in your
machine. You can set a limit with +RTS -M, but there isn't one by
default. So what happens when you write a program with a space leak
On Tue, 2008-02-19 at 12:22 +, Adrian Hey wrote:
To be honest, in all my years of Haskelling I can't think of a single
occasion where I've had a program get stuck in an infinite loop. I've
had plenty of stack overflows, and they're reported on the mailing
lists pretty regularly, but on
Stefan O'Rear wrote:
On Mon, Feb 04, 2008 at 10:13:12PM +, Adrian Hey wrote:
Also
remember that this behaviour never wastes more than 50% of the stack,
which is a relatively small amount.
Only if the stack is relatively small. Would you say the same about
heap, or about a stack that only
Adrian Hey wrote:
I have no objection to people bounding their stack if that's their
choice. I can't imagine why anybody who stopped to think about this
would actually want this feature, but it's free world.
What I object to is it being bounded by default to something other
than overall
