javap and nullable projection types.
maurizio.cimadamore at oracle.com
Fri May 10 12:35:26 UTC 2019
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.
Question: I guess the need for V? to have 'same old, same old' LV
contract arises from migration?
More information about the valhalla-dev