----- Mail original -----
> De: "Brian Goetz" <brian.go...@oracle.com>
> À: "Remi Forax" <fo...@univ-mlv.fr>
> Cc: "valhalla-spec-experts" <valhalla-spec-experts@openjdk.java.net>
> Envoyé: Vendredi 6 Décembre 2019 22:59:07
> Objet: Re: IdentityObject and InlineObject
>> Currently something typed Object represent either any or ref, we decide that
>> most of the Object represents any, so we still have to change some of the
>> Object that represent ref.
>
> Keep pulling on this string .. exactly WHAT will have to change? Let's
> have some specific examples, and then we can talk about how common they
> will be, and whether there are not other mitigating options. I worry
> you may be assuming something that isn't there.
package java.util;
public class IdentityHashMap<E extends IdentityObject> { ... }
package java.io;
public class IOReader {
protected IdentityObject lock;
...
}
package java.awt;
public class Component {
public IdentityObject getTreeLock() { ... }
...
}
and so on.
Rémi
