Deprecation warnings

Remi Forax forax at
Wed Feb 1 22:10:26 UTC 2017

it's in preparation of the addition of value type. Being able to retrofit Integer to a value type may never occur (you loose the identity) but if we want to have a chance to try, the direct call to its constructor has to be deprecated.


On February 1, 2017 7:55:57 PM GMT+01:00, Tom Rodriguez <tom.rodriguez at> wrote:
>Doug Simon wrote:
>>> On 1 Feb 2017, at 19:42, Andrew Haley<aph at>  wrote:
>warning: [deprecation] Integer(int) in Integer has been deprecated
>>> 		literals.put("return", new Integer(17));
>>> There are too many of these.  Shall I just fix them all?
>> No - we’re stuck with those because these methods are not deprecated
>on jdk8. So if you use SuppressWarnings, you’ll get a warning on jdk8
>about an unnecessary suppression!
>Well they can be changed to use valueOf instead, though for test cases
>think we'll need to make sure we don't actually care about object 
>identity.  Those I think we're stuck with.  That's going to be a very 
>painful deprecation warning for lots of people.

Sent from my Android device with K-9 Mail. Please excuse my brevity.

More information about the graal-dev mailing list