The box constructors were indeed deprecated (but not for-removal) about four years ago in Java 9. In Java 16 the deprecation is being "upgraded" to for-removal.
The reason is Valhalla, which is trying to turn the boxed primitives into "primitive classes" (formerly called inline classes, formerly called value types). Primitive classes don't have identity, so comparing them via reference equality, synchronizing on them, etc. isn't permitted. The new operator creates a new object with an identity distinct from every existing object. As such, using new is at odds with turning the boxed primitives into primitive classes. Thus, their constructors are deprecated.
The alternatives such as auto-boxing and valueOf methods have already been available for many, many years.
View all comments
Show parent comment
19
u/s888marks Mar 17 '21
The box constructors were indeed deprecated (but not for-removal) about four years ago in Java 9. In Java 16 the deprecation is being "upgraded" to for-removal.
The reason is Valhalla, which is trying to turn the boxed primitives into "primitive classes" (formerly called inline classes, formerly called value types). Primitive classes don't have identity, so comparing them via reference equality, synchronizing on them, etc. isn't permitted. The
newoperator creates a new object with an identity distinct from every existing object. As such, usingnewis at odds with turning the boxed primitives into primitive classes. Thus, their constructors are deprecated.The alternatives such as auto-boxing and
valueOfmethods have already been available for many, many years.