Chong Yidong <cyd@stupidchicken.com> writes: > Hmm, there is a problem, though. If we attempt to avoid a stack > overflow in `apply' by using the heap rather than the stack to store > large numbers of arguments, those arguments are invisible to the > stack-marking gargbage collector. Never mind, I got confused. SAFE_ALLOCA uses record_unwind_protect, so it's gc safe.