On 08/27/2013 03:51 PM, Martin Buchholz wrote:
On Tue, Aug 27, 2013 at 3:00 AM, Paul Sandoz <paul.san...@oracle.com> wrote:
[...]
Note that j.u. classes are quite inconsistent in this respect to using
diamonds and @Overrides. My preference is to do a sweeping change to all
such code.
For jsr166, we continue to maintain some support for jdk6 and use javac6 in
places, and so we've been known to de-<> for portability. We're also not
huge fans of using @Override pervasively.
From a reader perspective, @Override is great to figure out which part
of the code
is part of the supertypes contract and which part is specific to the class.
Rémi
