RFR(m): 8145468 deprecations for java.lang

Martin Buchholz martinrb at google.com
Thu Apr 14 17:10:19 UTC 2016

I've been tempted by the dark side, when a class needs a value AND a
lock (or an "identity").  Instead of doing

final String val = "foo";
final Object lock = new Object();

one can "optimize" this ("why can't we have both?") to

final String valAndLock = new String("foo");

and there are surely folks out there doing this.  We should probably
never remove those constructors.

More information about the core-libs-dev mailing list