Concat and zip
joe.bowbeer at gmail.com
Wed May 1 14:05:00 PDT 2013
I do foresee wanting to use zip in Java8, I don't want to write it myself,
and I'm not worried about transportation problems (how much worse than
Python can it be?).
On Wed, May 1, 2013 at 1:43 PM, Brian Goetz <brian.goetz at oracle.com> wrote:
> Yes, a key aspect of this YAGNI suggestion is that this is one of the
> things people CAN do for themselves, possibly with an example. And,
> because there are multiple ways to do zip (pad out shorter stream to size
> of longer stream, stop at end of shorter stream, throw if streams are not
> of equal length) people may well want to roll their own.
> On 5/1/2013 4:25 PM, Tim Peierls wrote:
>> On Wed, May 1, 2013 at 4:03 PM, Joe Bowbeer <joe.bowbeer at gmail.com
>> <mailto:joe.bowbeer at gmail.com>**> wrote:
>> In defense of zip: I think it is fairly important. Ease of
>> expression (and productivity) are still the most valuable benefits
>> of new features, and zip is important for a class of problems. zip
>> exists in Python, Scala, and Groovy (as "transpose" method), to name
>> a few.
>> I would keep zip without Int/Long/Double versions. This also avoids
>> all the varieties of mixed primitive/Object pairings in zipped
>> That sounds reasonable. I was going to say make the ref/ref version an
>> example in javadoc and then people can roll their own primitive/ref
>> versions, but maybe that's asking too much.
More information about the lambda-libs-spec-observers