search

yogendra-aurospaces / google-collections

Automatically exported from code.google.com/p/google-collections
Apache License 2.0
0 stars 0 forks source link

Remove all the higher-order functions and support classes from the library #231

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Seems to me like filter, transform, Function, Predicate, etc. could be
better off implemented in their own library. Here are some reasons why this
might be a good idea...

1. Many users would want to use google-collections without (or their own
implementation of) a 'functional' library. This would help avoid the
situation where a large code base ends up using a mix of libraries (which
can all too easily happen, even with the best intentions).

2. The new library could be dedicated to its purpose rather than what seems
to be just a limited add-on at the moment. c.f.
http://code.google.com/p/google-collections/issues/detail?id=218&q=reduce#c5.

Just wondering what others think about this...

Original issue reported on code.google.com by ada...@gmail.com on 6 Sep 2009 at 10:11

GoogleCodeExporter commented 9 years ago 
I wish. :)

However, I think it's too late to yank this much functionality that many users 
do 
love.

Original comment by kevin...@gmail.com on 8 Sep 2009 at 9:25

GoogleCodeExporter commented 9 years ago

Original comment by kevin...@gmail.com on 17 Sep 2009 at 4:51