Feature #5044

#zip with block return mapped results

Added by trans (Thomas Sawyer) almost 7 years ago. Updated 4 months ago.

Target version:


Is there any reason that #zip doesn't return results like map?

[1,2,3].zip([1,2,3]){ |a,b| a + b } #=> [2,4,6]

Currently, it just returns nil, which seems rather contrary to the return result of the non-block form.

Related issues

Related to Ruby trunk - Feature #4539: Array#zip_withAssigned


#1 [ruby-core:38165] Updated by Eregon (Benoit Daloze) almost 7 years ago


Please have a look at (or ).

The reason is explained by Yusuke in :

2011/4/5 Benoit Daloze

An unconditional nil is anyway not useful here, the only concern I see
might be the cost of creating this Array.

It is actually a problem.
I have used Array#zip with block for iteration many times. do |x, y|
p [x, y]

The change requires some people (including me) to rewrite
such a code as follows:

big_ary1.size.times do |i|
x, y = big_ary1[i], big_ary2[i]

So I like zip_with, if it is really needed.

That issue kind of got lost, it is probably a good idea to continue it.

For your example, we could have [1,2,3].zip_with([1,2,3], :+)

#2 [ruby-core:43654] Updated by akr (Akira Tanaka) about 6 years ago

Currently it can be implemented as follows.

% ruby -e 'p [1,2,3].zip([1,2,3]).map {|a,b| a + b }'
[2, 4, 6]
% ruby -e 'p [1,2,3][1,2,3]).map {|a,b| a + b }.to_a'
[2, 4, 6]

#3 [ruby-core:43653] Updated by mame (Yusuke Endoh) about 6 years ago

  • Status changed from Open to Assigned
  • Assignee set to matz (Yukihiro Matsumoto)

#4 [ruby-core:49720] Updated by mame (Yusuke Endoh) over 5 years ago

  • Target version set to 2.6

#5 Updated by naruse (Yui NARUSE) 6 months ago

  • Target version deleted (2.6)

#6 [ruby-core:85684] Updated by matz (Yukihiro Matsumoto) 4 months ago

  • Status changed from Assigned to Rejected

We cannot change the behavior. The change would increase the memory consumption (and decrease the performance).


Also available in: Atom PDF