Re: Threads and asyncs

[Tom Lord]

       > In C,  you don't have grabbable continuations 

or closures.  Though, sure, closures don't capture entire activation
records.



        > In the straightforward, always allocate from the heap
        > model, the GC is always responsible for collecting activation
        > records.  

Right -- but, as SCM illustrates or points-towards, you can still
treat them specially.


      > Thus we have strictly improved the speed (because popping the
      > stack is about the fastest deallocation anybody will ever
      > have, other than exiting, of course).

Spaghetti stacks speak to this issue.


      > Better?

Totally clear.

-t