> In practice, you never really needed it, since you could run your program a few times, see what the high water mark of your heap was, then set the precise siz

> In practice, you never really needed it, since you could run your program a few times, see what the high water mark of your heap was, then set the precise size at compile time. How would this work with anything that has unknown runtime memory cost? Say an editor of any kind? Like an image editor with undo buffers.