commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rijk van Haaften" <r.j.c.vanhaaf...@gmail.com>
Subject Re: Commons Collections & Java 5
Date Tue, 20 Nov 2007 09:44:52 GMT
> Tickets and patches - see
> https://issues.apache.org/jira/browse/COLLECTIONS/fixforversion/12312131.
>
> Thanks for the interest - look forward to your input.  Apologies in
> advance for the speed ... I'm the only real committer at the moment, and
> do not have much time to spare - however, I am trying to get something
> done on it every week.


Before I start coding, I think I need to know a little more backgrounds. The
release-notes say:

For commons-collections, we have chosen to break the API in various ways.

I consider this the right thing to do. However, a major issue I expect is
that the java.util
Collection classes were carefully designed to stay backwards-compatible as
much as
possible. That decision causes the java collection classes to be only half
generic which
leaves us with several unchecked warnings that can not be worked around.

Are we going to adhere to their choices or are we going to build the first
fully generic
java collection library?

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message