(missing)
Re: Make code safe for continuation capture, part the first. · gambiteer/srfi-231@2876863 Bradley Lucier (04 Aug 2022 17:09 UTC)

Re: Make code safe for continuation capture, part the first. · gambiteer/srfi-231@2876863 Bradley Lucier 04 Aug 2022 17:09 UTC

On 8/4/22 9:19 AM, Marc Feeley wrote:
> It has the nice features of not adding pressure on the GC (no heap garbage generated) and being call/cc and thread “safe”.

Does Gambit not copy stack frames to the heap during a GC?

I agree that the default management of data on the stack is easier and
faster than managing data on the heap, but if enough stack frames are
pushed that a GC is triggered, then that data has to be managed somehow.

Brad