javap and nullable projection types.

Remi Forax forax at univ-mlv.fr
Fri May 10 13:42:34 UTC 2019


----- Mail original -----
> De: "Maurizio Cimadamore" <maurizio.cimadamore at oracle.com>
> À: "John Rose" <john.r.rose at oracle.com>
> Cc: "valhalla-dev" <valhalla-dev at openjdk.java.net>
> Envoyé: Vendredi 10 Mai 2019 14:35:26
> Objet: Re: javap and nullable projection types.

> On 09/05/2019 21:23, John Rose wrote:
>> Thus, any given "LV;" in a classfile might either be some
>> classic C, or some V? for an inline V.
> 
> For javac this is a non-issue, given that javac can see whether V is a
> value or not, and hence infer the '?'-ness.
> 
> For javap is more problematic to do so, given that javap doesn't have
> all the code.

it's time to resurrect the attribute ValueType ?

> 
> Question: I guess the need for V? to have 'same old, same old' LV
> contract arises from migration?
> 
> Maurizio

Rémi


More information about the valhalla-dev mailing list