Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
Here's the bench mark for both methods.
@mortonfox, As I said it's a good solution. I think the comments section is a good place to discuss tradeoffs that may not be obvious to evey user, such as performance issues. That way someone seeing these for the first time can make the best informed decision in the future.
The main thing this is good for is being concise. I never believed it was performant since Ruby has special optimization for blocks.
Clever is the tag chosen by Codewars; this wasn't some kind of slight. It's a good solution, but performance is sub-optimal and the better performing solution is also easier to read.
And to say "As for performance, don't use Ruby", that's just silly. It doesn't matter what language someone is developing in performance should be a consideration. This isn't a case of pre-mature optimization. It's an easy performance gain. I provided the benchmark for anyone that might come along in the future to be helpful as they may not be aware of the performance difference.
It's not 'clever', it's perfectly readable to any Ruby developer. You could argue that so many things in ruby are not readable to 'the average developer'.
Passing just the method is more common in many other languages, be it Python, Scheme, Haskell, Dart, Smalltalk or even C.
As for performance, don't use Ruby, or optimize inner loops. For most Enumerable#map operations the actual operation will cost way more than iterating in whatever way.
This is certainly a clever solution and deserving up the the up votes for that. I'm surprised that this is so heavily upvoted though for "Best Practices", in comparison to the more direct map enumeration version here http://www.codewars.com/kata/reviews/5356b77a2930ee4c010007e6/groups/5397a4c4c20318c06e000ea0
While this technique is certainly clever, I don't believe it is as readable to the average developer and the performance is worse.
The results posted below are from benchmarking this solution against the standard map enumerable. This
to_proc
version shown here is about 8% slower. So you lose speed and code legibility.Learned something here. Great example. Time to mess around in the REPL some more...
A little digging brought me to Stack Overflow (http://stackoverflow.com/questions/1961030/ruby-ampersand-colon-shortcut). It's a really cool functionality, and I'm glad I know it now!
Read up on the unary & operator. It's operating on the :capitalize symbol. Basically it's making the captialize method into a block.
It's leaning on functionality of
Symbol#to_proc
to do it. There's a few different pieces that make it up, and http://www.jacopretorius.net/2012/01/symbolto_proc-in-ruby.html seems to be a good in depth writeup of it.In short though:
&foo
in arguments passesfoo
as a block to the method as if you'd done{ foo.call }
. If foo isn't a proc, it callsto_proc
on it first.Symbol#to_proc
is implemented and creates a proc that sends the symbol to the block argument. That is:capitalize.to_proc
returns a proc (block) equivilent to{ |arg| arg.capitalize }
[].map { |element| element.capitalize }
can be written as[].map(&:capitalize)
and it returns the same result.I don't understand it. Doesn't Array#map accept a block as an argument? What is the syntax for "&:capitalize"?