[e-lang] makeProxy reveals implicit sendOnly

[Mark S. Miller]

Mark S. Miller wrote:
> Kevin Reid wrote:
>> I had understood that it is intended that <- is optimized to sendOnly  
>> when the result is not used; if so, then either the conditions for  
>> this optimization must be well-defined, or makeProxy must be unsafe.
> 
> Good catch. I think I agree that these are the only viable choices. Of the 
> two, I mildly prefer the first: we should specify the conditions in which this 
> optimization happens.


I see a third valid possibility that I don't like, but explain only for 
completeness:

We could have two makeProxy primitives. A safe one which cannot distinguish 
between send and sendOnly, and an unsafe one which can.


-- 
Text by me above is hereby placed in the public domain

     Cheers,
     --MarkM