Closed GoogleCodeExporter closed 9 years ago
If you're feeling even more ambitious...:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6368844
(I haven't actually looked at the links, but perhaps you're interested)
Also, IIRC, Josh's presentation on the new collection types said something like
"ArrayDeque: default List implementation in JDK7?" So you may want to talk to
him if
you haven't already to see whether that question mark meant "if we get around
to it"
or "if we resolve this exceptionally hairy issue." I wouldn't be surprised if
there's a question of whether it's kosher for a Deque to allow random access,
though
that didn't seem to stop them with LinkedList and the Queue interface.
Original comment by cpov...@google.com
on 25 Jun 2008 at 10:34
Martin and Josh and I were chatting about this very thing a week or two ago and
none
of us could really come up with, off the top of our heads, why any puppies
would get
killed if ArrayDeque implemented List.
Original comment by kevin...@gmail.com
on 25 Jun 2008 at 10:57
There's one reason why the JDK ArrayDeque can't be modified to implement List.
Doing
so would change its equal() and hashCode() behavior.
Original comment by jared.l....@gmail.com
on 25 Jun 2008 at 11:02
... which neither ArrayDeque nor the Deque interface specify. So that's not
necessarily a deal-breaker.
Original comment by kevin...@gmail.com
on 25 Jun 2008 at 11:08
This probably isn't worth implementing, considering the lack of interest and our
reluctance to add dependencies on Java 6.
Original comment by jared.l....@gmail.com
on 8 Apr 2009 at 4:13
Original comment by kevin...@gmail.com
on 17 Sep 2009 at 6:02
This issue has been moved to the Guava project (keeping the same id number).
Simply replace 'google-collections' with 'guava-libraries' in your address
bar and it should take you there.
Original comment by kevinb@google.com
on 5 Jan 2010 at 11:09
Original issue reported on code.google.com by
jared.l....@gmail.com
on 25 Jun 2008 at 10:16