-
Enhancement
-
Resolution: Duplicate
-
P3
-
1.4.2, 6
-
generic, x86
-
generic, windows_xp
Name: tb29552 Date: 10/22/2003
A DESCRIPTION OF THE REQUEST :
We should encourage people to move from "new Boolean()" to Boolean.TRUE, Boolean.FALSE by deprecating the constructor and documented the aforementioned alternative methods.
JUSTIFICATION :
Using Boolean.TRUE, Boolean.FALSE leads to improved performance, reduced memory footprint. Many developers are unaware of this recent addition and continue to use the constructor. A deprecation should formalize this migration route.
(Review ID: 216908)
======================================================================
A DESCRIPTION OF THE REQUEST :
We should encourage people to move from "new Boolean()" to Boolean.TRUE, Boolean.FALSE by deprecating the constructor and documented the aforementioned alternative methods.
JUSTIFICATION :
Using Boolean.TRUE, Boolean.FALSE leads to improved performance, reduced memory footprint. Many developers are unaware of this recent addition and continue to use the constructor. A deprecation should formalize this migration route.
(Review ID: 216908)
======================================================================
- duplicates
-
JDK-8145468 update java.lang APIs with new deprecations
-
- Resolved
-
- relates to
-
JDK-4302078 Boolean should have a static factory valueOf(boolean)
-
- Closed
-
-
JDK-4262398 Avoid creating new Booleans for increased operational speed
-
- Resolved
-
-
JDK-6428760 Need Annotation @Denigrated
-
- Closed
-