[ruby-core:46050] [ruby-trunk - Feature #6483] parametric map

Issue #6483 has been updated by prijutme4ty (Ilya Vorontsov).


Thank you for much more elegant code. It works with all of my specs except one:
['abc','cdef','xy','z','wwww'].select(&:size.() == 4)    # ==> ['cdef', 'wwww']

It looks that one cannot make this work without proxy object.

nobu (Nobuyoshi Nakada) wrote:
> =begin
> In ((%golf_prelude.rb%)):
> 
>   class Symbol
>     def call(*args, &block)
>       proc do |recv|
>         recv.__send__(self, *args, &block)
>       end
>     end
>   end
> 
> It might use (({public_send})), indeed.
> =end
----------------------------------------
Feature #6483: parametric map
https://bugs.ruby-lang.org/issues/6483#change-27656

Author: prijutme4ty (Ilya Vorontsov)
Status: Assigned
Priority: Normal
Assignee: matz (Yukihiro Matsumoto)
Category: 
Target version: 


I found very common use-case for map: map with parameters and &:meth syntax. For example:
matrix =[[1,2,3],[4,5,6]]
matrix.pmap(' ',&:join).join("\n") # => "1 2 3\n4 5 6
[1,2,3,4,5].pmap(2, &:to_s) # ['1', '10', '11', '100', '101']

[1,2,3,4,5].pmap(&:to_s) # ['1', '2, '3', '4', '5'] # empty parameter list behaves as usual map

Isn't it much better than ugly and verbose code: 
matrix.map{|line| line.join(' ')}.join("\n")

I can write simple implementation 
class Proc
  def curry_except_self(*args)
    Proc.new{|slf| curry[slf,*args] }
  end
end

module Enumerable
  def pmap!(*args,&block)
    map! &block.curry_except_self(*args)
  end
  def pmap(*args,&block)
    dup.pmap!(*args, &block)
  end
end

Use-cases can be rewritten as tests (I can send my own unit-test if needed)


Also I've two related things to discuss.
1) First is &-syntax. Is it possible to change ruby-interpeter in such a way that &:proc could be at any place. matrix.pmap(&:join,' ') is much prettier than matrix.join(' ',&:join) What is the reason behind this restriction? And if one can remove this restriction, we'd have new nice syntax.
2) I'm not very experience in functional programming with curry etc, but it seems to me that currying proc without supplying first argument(self) can be common task when &:meth syntax is in play. If so, may be my curry_except_self(*args) also should be included in ruby.


-- 
http://bugs.ruby-lang.org/