Re: the state of the concurrency branch

[Stefan Monnier]

>> I think a typical reason to do this kind of funny business is to
>> communicate from the timer (or process filter or whatever) back to
>> the caller.
> For this use case, wouldn't a feature for thread futures be appropriate?

For process filters/sentinels, you can almost always replace the
dynamically scoped variable with a process property.

We could add timer properties for that same purpose.  Tho, there are
already many other ways to get the same result without relying on
dynamic bindings.


        Stefan