[e-lang] multiway when-catch

[Kevin Reid]

On Nov 1, 2007, at 21:47, Dean Tribble wrote:

> On 11/1/07, Mark Miller <erights at gmail.com> wrote:
>> On Nov 1, 2007 2:49 PM, Kevin Reid <kpreid at mac.com> wrote:
>>>    1. f will not be invoked until x *really is* completely resolved
>>> (as defined by Ref.isResolved), rather than when it is more-resolved
>>> or pretending to be resolved.
>>>    2. f will be invoked at most once.
>>>    3. f will be passed a reference which is the same as x.
>>> There are probably other reasons I haven't thought of (MarkM?).
>>
>> That's all I can think of.
>
> Is there a guarantee (in Ref.whenResolved(x, f)) that f will not be  
> revealed to x?

Necessarily, yes. All three properties are false if x's unspecified  
behavior is allowed access to f.

-- 
Kevin Reid                            <http://homepage.mac.com/kpreid/>