Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
There is no information on how to process non-numeric strings (like
"fiv"
) in the tests: it seems we're supposed to ignore them from the sum.This comment is hidden because it contains spoiler information about the solution
Are you sure
"hello"
has only 12 anagrams?Also: I'm not sure because the site doesn't show it clearly, but it seems there are several katas which have the same leitmotif as this kata (or can be reduced to such).
The third test for the fixed case of vectors having zero has an incorrect test message: it should be
f"Input: {4,4,0,4}"
, notf"Input: {0,1,6,0}"
— probably copypasted?Ruby fork which resolves the issue below me (link) + simplifies the test coding.
P.S. Oh and also if this fork will be approved, I think I'd like to try implementing fixes for the other issue (this one, under spoiler tag), if nobody is against it :)
Seems like that's the bug for Ruby testing; raised an issue about that
Ruby testing is broken: even if you solve the kata without regex, it requires from you to put smth inside of it, or else it drops the error
No examples found
. For other languges this problem does not exist though.I think that the cases with one word can be considered either as first name or surname, BUT not the both at the same time, so it should be obvious it's invalid.
(I know there are people which surname and personal name are identical, but it's not the case for this kata though.)
It seems this problem has been fixed by itself or by someone; either way, couldn't reproduce that rn, so resolved
Java: created fork which output value is HashMap, as stated in the description, and which resolves this issue.
P.S. The solutions with int[] shouldn't be invalidated, because backward compatibility for
int[]
has been implemented as well.approved :D
Coffeescript and Swift got their random tests by someone; the problem with JS still stands tho
Swift: the structure can be changed by user so with some hijinks you can cheat out all tests (one of possible ways to do that is here).
P.S. OG issue by zLuki: here
Should be resolved now
Even though it's now retired, the fixed test about transfering 0.25 ETH to LTC is wrong, because it's not equal 0.0144 LTC, but 0.0955...
Also yeah, money conversion using floats is not the best idea imo
Loading more items...