News for hackers. Stuff that matters.
Re:Nimrod by Example by camperman on Thursday July 17, 2014 @01:14PM (#8048810)
Nimrod's pointers to garbage collected memory are separate from the pointers you can allocate yourself. So you could do manual memory management on the parts that really need it - say for a game in a tight loop - and leave the collector to worry about the smaller and less time-critical stuff.

Also the GC is only triggered on a memory allocation. It doesn't run in a background thread or anything like that. So if the GC fails, then the allocation of memory fails (as I understand it) which means your scenario would be caught early.

Re:Nimrod by Example by Dewie on Thursday July 17, 2014 @02:13PM (#8049178)
> Nimrod's pointers to garbage collected memory are separate from the pointers you can allocate yourself.

Does this mean that they use different heaps?

Re:Nimrod by Example by flaviu1 on Thursday July 17, 2014 @02:48PM (#8049393)
No, they are on the same heap since the GC isn't a moving collector.
Re:Nimrod by Example by eudox on Thursday July 17, 2014 @02:37PM (#8049324)
They probably use the same heap underneath.