On Wed, 2008-04-16 at 11:00 +0530, Abhay Parvate wrote:
Your mail gives me an idea, though I am not an iota familiar with
compiler/garbage collector internals. Can we have some sort of
internally maintained priority associated with allocated objects? The
garbage collector should look at these
Hello Abhay,
Wednesday, April 16, 2008, 9:30:34 AM, you wrote:
i think it will not work with current ghc GC - it scans entire
memory/nursery when garbage collected so anyway you will need to wait
until next GC event occurs
Your mail gives me an idea, though I am not an iota familiar with
I am not saying that it should claim it as soon as it is unused; all I am
saying that as soon as a priority object becomes unreferenced, it should be
the first choice for collecting in the next collect.
Further I was under the impression (I may be wrong) that it uses a
generational GC and
Hello Abhay,
Wednesday, April 16, 2008, 10:51:07 AM, you wrote:
I am not saying that it should claim it as soon as it is unused;
all I am saying that as soon as a priority object becomes
unreferenced, it should be the first choice for collecting in the next
collect.
on the GC, all
Thanks, both for the summary and for the link. Will try to go through it.
Regards,
Abhay
On Wed, Apr 16, 2008 at 12:37 PM, Bulat Ziganshin [EMAIL PROTECTED]
wrote:
Hello Abhay,
Wednesday, April 16, 2008, 10:51:07 AM, you wrote:
I am not saying that it should claim it as soon as it is
Are Haskell folks satisfied with the practical necessity of imperatively
explicitly reclaiming resources such as file handles, fonts brushes, video
memory chunks, etc? Doesn't explicit freeing of these resources have the
same modularity and correctness problems as explicit freeing of system
Your mail gives me an idea, though I am not an iota familiar with
compiler/garbage collector internals. Can we have some sort of internally
maintained priority associated with allocated objects? The garbage collector
should look at these objects first when it tries to free anything. The
objects
