> Option 2: RefObject, ValObject - interfaces
>VM at class definition adds RefObject to all existing classes
>value classes required to declare ValObject as superinterface
>
>ackwardness: VM needs special behaviors for Object.wait, Object.notify -
> if dynamically a ValObject, throw
I see two options proposed:
Option 1: RefObject, ValObject - classes
VM at class definition time replaces superclass of all existing classes from
Object -> RefObject
VM translates:
new Object -> treated as Object.new() { returns RefObject.new() } //
assume old code only wants
> I think i still prefer having interfaces Val/Ref instead of classes, these
> interfaces can be injected by the VM, at least the Ref interface can be
> injected, for the Val interface, we can requires all value types to implement
> that interface.
I view using interfaces instead of classes
> De: "John Rose"
> À: "Remi Forax"
> Cc: "Karen Kinnear" , "valhalla-spec-experts"
>
> Envoyé: Mercredi 30 Janvier 2019 00:29:01
> Objet: Re: Valhalla EG notes Jan 16, 2019
> On Jan 29, 2019, at 11:10 AM, Remi Forax < [ mailto:fo...@univ-mlv.fr |
> fo...@univ-mlv.fr ] > wrote:
>> currently
> De: "John Rose"
> À: "Brian Goetz"
> Cc: "valhalla-spec-experts"
> Envoyé: Mercredi 30 Janvier 2019 01:20:50
> Objet: Re: Valhalla EG notes Jan 16, 2019
> On Jan 29, 2019, at 12:27 PM, Brian Goetz < [ mailto:brian.go...@oracle.com |
> brian.go...@oracle.com ] > wrote:
>> But, now we a
