News for hackers. Stuff that matters.
Re:Carp – A statically typed Lisp, without a GC, for real-ti... by pjc50 on Friday October 15, 2021 @08:32AM (#28877020)
That's a question for the underlying allocator, surely?

(Quite often the answer is "it isn't")

Re:Carp – A statically typed Lisp, without a GC, for real-ti... by andi999 on Friday October 15, 2021 @02:38PM (#28881370)
Not just for the allocator. I always thought a main point of a garbage collector was heap compactification (shuffling things around so there is more space), but maybe I am wrong.
Re:Carp – A statically typed Lisp, without a GC, for real-ti... by cmrdporcupine on Saturday October 16, 2021 @09:17AM (#28887671)
Nah, only copying / generational collectors do heap compactification. A simple Mark&Sweep collector doesn't, for example. Nor does reference counting. Both of which are used by many Lisp or Lisp-like languages.

Nothing can substitute for a really good allocator.

Re:Carp – A statically typed Lisp, without a GC, for real-ti... by andi999 on Saturday October 16, 2021 @10:59AM (#28888305)
So what happens to long running lisp programs? Running out of memory due to fragmentation eventually?
Re:Carp – A statically typed Lisp, without a GC, for real-ti... by xxs on Saturday October 16, 2021 @11:14AM (#28888420)
One would expect at least a provision for a stop the world phase. where all mutator threads get to wait for a massive defragmentation.
Re:Carp – A statically typed Lisp, without a GC, for real-ti... by xxs on Saturday October 16, 2021 @02:46AM (#28886031)
Not every GC has compaction phase though, but generational ones do by design.