This translation is too old and out of date, best to start over fresh.
Used KaTeX in description + Enabled Ruby 3.0 in this fork
Fixed.
Your solution has a bug, it does not handle some characters correctly. You need to read the description once again.
It is not a kata issue.
Without knowing what language you try, what is your code, and what is the input of the failed tests we have no way of knowing what you're doing wrong.
expected:<1307> but was:<1275>
But when I print my result right before I return it, it shows the correct value.
That's a twoliner though.
Approved
I had a lot of fun with this one :)
wow made a functionnal oneliner that actually is pythonic... yay
python new test framework is required. updated in this fork
In the Java version, the given basic and other unit tests have the assertion parameters in reverse order. The expected value must be the first parameter and the actual value the second parameter.
Loading collection data...
This translation is too old and out of date, best to start over fresh.
Used KaTeX in description + Enabled Ruby 3.0 in this fork
Fixed.
Your solution has a bug, it does not handle some characters correctly. You need to read the description once again.
It is not a kata issue.
Without knowing what language you try, what is your code, and what is the input of the failed tests we have no way of knowing what you're doing wrong.
expected:<1307> but was:<1275>
But when I print my result right before I return it, it shows the correct value.
That's a twoliner though.
Approved
I had a lot of fun with this one :)
wow made a functionnal oneliner that actually is pythonic... yay
python new test framework is required. updated in this fork
In the Java version, the given basic and other unit tests have the assertion parameters in reverse order.
The expected value must be the first parameter and the actual value the second parameter.
python new test framework is required. updated in this fork
Approved
python new test framework is required. updated in this fork
Loading more items...