Re: why asyncs were created

[Tom Lord]

        > As a clarification, I have in mind to keep the "async" name and the
        > "async" behavior, but an async does not need to continue to be an
        > opaque object; it could just be a normal procedure that is used in a
        > special way.


Ah -- a representation issue, not a semantic issue?

What replaces the `got_it' flag in an async object?  I.e., the bit 
that says an async needs to be run, but could not be run when the
low-level or user-supplied signal was delivered?

-t