hg: valhalla/valhalla: 8222634: [lworld] Javac sometimes emits incorrect ('Q') descriptors for fields.

[Srikanth]

On 17/04/19 6:45 PM, Karen Kinnear wrote:
> Srikanth,
>
> Just making sure I get it ...
>> On Apr 17, 2019, at 9:10 AM, Tobias Hartmann <tobias.hartmann at oracle.com> wrote:
>>
>> Hi Srikanth,
>>
>> On 17.04.19 15:03, Srikanth wrote:
>>> This change set fixes 4 problems you had reported in https://bugs.openjdk.java.net/browse/JDK-8222634:
>> Thanks, I can confirm that these problems are now fixed.
>>
>>> I have upgraded the javac tests to include these scenarios. I will also be adding more tests in
>>> future as I test and upgrade the preliminary support that has been put in place.
>>>
>>> Here are the pending ones I see:
>>>
>>> (1) Compile time null assignment to values should be tolerated (?)
> For MyValue1? null assignment is ok.
> For MyValue null assignment should not be tolerated at compile time
>
> Is that what you are expecting?

Yes Karen and that matches tip behavior ATM.

Thanks
Srikanth
> thanks,
> Karen
>
>>> (2) Compiler does not tolerate the following:
>>> MyValue1?[] vBoxArray = new MyValue1?[42];
>> Right, both cases did work with .box declarations.
>>
>> Best regards,
>> Tobias