hg: mlvm/mlvm/jdk: meth: add proxy maker for closures
Rémi Forax
forax at univ-mlv.fr
Wed May 26 07:14:57 PDT 2010
Le 26/05/2010 15:05, Attila Szegedi a écrit :
> On 2010.05.25., at 22:57, Charles Oliver Nutter wrote:
>
>
>> On Tue, May 18, 2010 at 4:44 PM, Rémi Forax<forax at univ-mlv.fr> wrote:
>>
>>> [...]
>>>
>>>
>>>> One important question for me is how multi-method interfaces would be
>>>> handled. I had originally tried to use Scala's "Function" interfaces
>>>> in Duby to represent closures, but they all have multiple abstract
>>>> methods that must be handled completely differently. I'd need to
>>>> provide my own superclass with default behavior or have a way to
>>>> stitch together N handles for N abstract methods.
>>>>
>>>>
>>> You can construct a tree of method handles,
>>> like Attila's code does.
>>>
>> I'm not sure I understand how this would tie into implementing an
>> interface or abstract superclass with many methods...can you
>> elaborate?
>>
> Honestly, I can't work out either what's Rémi referring to :-)
>
> Attila.
>
I don't remember too.
Anyway, you don't have to implement all the methods, one is sufficient
if you can garantee that
there is a surjection between the set of possible signatures and the set
of possible methods.
Rémi
More information about the mlvm-dev
mailing list