Valhalla EG notes Jan 16, 2019

[Remi Forax]

----- Mail original -----
> De: "Karen Kinnear" <karen.kinnear at oracle.com>
> À: "valhalla-spec-experts" <valhalla-spec-experts at openjdk.java.net>
> Envoyé: Mardi 29 Janvier 2019 19:55:17
> Objet: Valhalla EG notes Jan 16, 2019

> Attendees: Remi, Tobi, Dan H, John, Brian, Simms, Fred, Karen
> Corrections welcome - thank you John for your summary notes
> 
> AIs:
>  Remi - write up why if we retrofit arrays for Arrays 2.0 specializable
>  interface,
> do we need covariance?
>  All: find examples where existing code assumes Class.getSuperClass() is
>  java.lang.Object explicitly, or other pain points due to reparenting existing
>  subclasses of Object with RefObject
>  John: question about RefObject handling please?
> John: val x - new Object() assert x instanceof RefObject;
> 
> ed. note - John - I don’t get the sentence above - I thought existing explicit
> java.lang.Objects
> would stay as supers of RefObject and ValObject, or did I miss context here?

Hi Karen,
currently the result of the expression "new Object()" is a reference type, so it should be a RefObject, but we have created an Object not a RefObject,
so it's at best weird. 

[...]

> 
> thanks,
> Karen

Rémi