The strings are all like "3:2". So it is "3" > "2" and 3 > 2. String comparison and integer comparison have the same result in this case.
Here the values are all single digits. The method fails if a string is like "12:8" because "12" < "8" and 12 > 8. However, two-digit results are not part of this kata.
Nice
This prob should eat less resources than .toString(), no?
genius
If someone just add 10 more words, this doesn't seem very scalable.
Nice solution
It is a string comparison.
The strings are all like "3:2". So it is "3" > "2" and 3 > 2. String comparison and integer comparison have the same result in this case.
Here the values are all single digits. The method fails if a string is like "12:8" because "12" < "8" and 12 > 8. However, two-digit results are not part of this kata.
Sorry that is not best practices, there is a formular for this problem, which is much more efficient.
We should ban it, it's illegal.
But X and Y would be string, right?, you just can compare them and the compiler knows that it should treat them as integers?
I HATE THIS SOLUTION!!!!!!!!
ITS SO @SS RIGHT?!!!
they deserved it
your solution is this one :|
this solution is so sh!t!!!
this solution is sh!t
Loading more items...