Had to graph out what was going on in this one. Super cool!

Great separation of concerns

This one is pretty clever, I have to say.

This is really cool and concise - you used all the same methods as my solution with 1/3rd the verbosity. I love kata tackles like this that make the most of Ruby's functional enumerable methods.

Props on writing the full method out. This is very easy to follow, too.

Now THIS is best practices. Beautiful!

Eloquent, simple, ideomatic.

Now that is concise!

hahahah this one made me laugh

I've moved my example test cases out of the description and into the example box and refactored a little bit. Thanks for the suggestion.

I don't know why this is being voted clever instead of best practices. The approach of preserving an operator lambda for later deployment is very intuitive and mimics the way an actual pad calculator would seem to work. I like that this solution didn't go for any out-of-the-box metaprogramming techniques and I really enjoy how concise it is.

This one was a lot of fun! I enjoyed seeing all the different approaches in the solutions.

I wouldn't go that far, but this did feel a bit gimped by the example :) Then again, I was prodded to learn more by how the example did NOT explain why the yielder parameter / infinite loop function the way they do in this context.