Fair. You're correct.

I tend to agree. Code that works when it shouldn't can be more dangerous as code that doesn't. Think in terms of someone sending what they believe is a boolean "false" but instead sends the string "false". Ruby will evaluate that as "true", so if this is meant to only get results from booleans (no matter how you nitpick Ruby's implementation of them) instead of how the passed value is evaluated by Ruby's definition of truthiness, there should probably be a case to make sure those either fail or return a discernable value like "false" or "nil" that could be used by anything calling it.

Codewars shouldn't be just about passing the tests. It should be about encouraging good practices.

Good for returning after a Boolean value is passed, but will also return for things that evaluate as true or false. At any level higher than 8, I'd suggest the test should probably be written to reject this solution, but it definitely fulfills the test criteria.

Created a fork and took care of the merge conflicts as far as I can tell.

I'll get on that later today. Thanks again! First time submitting a translation on here. Unfortuante that it's not a bit more directly git-like, or possibly if it utilized github since they offer that as a login option.

Fixed both. Thanks for reviewing it. Anything else you see?

Ruby translation available! please approve.

That's what I did, and why I listed it as an annoyance with the timeout and not an actual problem.

Which has literally nothing to do with my complaint. I did in fact achieve a more efficient solution, but often while coming up with a solution, one tests various things to see what is and isn't working, and that code is seldom as efficient. My issue is that the timeouts are annoying when experimenting since they prevent you from getting a result at all during that experiment.

my one annoyance with this one is that a lot of valid solutions would overrun the timeout codewars uses.

Submitted it again. Thanks for letting me know!

oops, cleanup didn't get pasted in

I didn't assume lowercase from the start since it wasn't specified.

Misclick. Didn't mean to submit it as final with the outputs still in place, see my other solution for what I meant to submit.