Looking at it now, I'd say you're right. '==' does indeed return a boolean.

There's no specific reason for explicitly stating true/false here. Just a rookie mistake that I never bothered to correct.

Is it good to state explicitly to return true/false?
I ommited that in my answer as I feel that the '==' sign already makes the return value a boolean

You can still submit it, but you'll have to rename your function to get it to pass.

^ Someone please fix the submission evaluation tests. Can't submit Ruby solutions :(

Nice simple challenge, I think attempting to code these in way that could be used in multiple applications is what makes it challenging.

Ruby tests and submission evaluation should use 'convert_temp' rather than 'convertTemp'.

Same here. Both example arrays in the introduction and all three test cases will pass with my solution, but I am receiving an error on submission.