Missing useful assertion messages

Just letting yall know

You just click the fork button and it will fix the merge conflict, who cares?

The ruby translation will need to start a new fork. I'll have to do that for Java too.

Solution setup should have some return value to act as a type hint, probably 0.0.

Oh nobody fixed the description yet.

I'll do that now.

Can you update the description with a ruby example? The default is clojure which doesn't look anything like ruby.

Can you add assertion messages for random tests?

There is no specification on recursive callbacks, e.g what happens if someone does

before :test_method :before1
before :before1 :before2

? If anything this kata is like a toy model: only works on a handful of very tiny examples, and not ready for any real world use.

You used my previous solution ;)

Been a very long time since I touched this, but it's string comparison to see if one string can be transformed into a second string only by adding, removing or swapping a single character.

With that said, we were apparently code golfing and optimizing performance just for fun, you should absolutely not take this code as a good example of well-written Ruby.

What is the actual purpose of "One Away"?.

To compare a pair of ranges, strings or arrays?.

Would appreciate some comments.

Many regards,

A very green Ruby rookie... :)

Maybe change the function nameto follow best practise, like equal_sum?.

awesome!but (d=='L') will be more readable.

As long as you provide an expression that is of boolean type, you can do it! :)