RFR : 7178639 : (XXS) Remove incorrect documentation from Deque.push(E e) (original) (raw)
Martin Buchholz martinrb at google.com
Tue Apr 30 01:21:21 UTC 2013
- Previous message: RFR : 7178639 : (XXS) Remove incorrect documentation from Deque.push(E e)
- Next message: new File(parent, child) when child is absolute
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Apr 29, 2013 at 6:14 PM, Mike Duigou <mike.duigou at oracle.com> wrote:
Looks reasonable to me. Could BlockingDeque::push() just use {@inheritDoc} for main body doc?
Perhaps. But as I wrote many years ago in the same source file,
/*
* We have "diamond" multiple interface inheritance here, and that
* introduces ambiguities. Methods might end up with different
* specs depending on the branch chosen by javadoc. Thus a lot of
* methods specs here are copied from superinterfaces.
*/We found that @inheritDoc is far too often not exactly what we wanted.
- Previous message: RFR : 7178639 : (XXS) Remove incorrect documentation from Deque.push(E e)
- Next message: new File(parent, child) when child is absolute
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]