I really like this kata, thank you! One note - I wish the prompt had any context whatsoever other than don't use BigInt. I'm trying to strengthen my understansing of algos, and I'm down a rabbit hole researching how javascript objects work under the hood and working my way up in inheritence. If this was a little more focused, without giving away too much, it could be super helpful for my learning. I may be going too deep and little doses of understanding and building on that would be better pedogocially speaking. Maybe a way to frame the prompt in a way to build off some intermediate knowledge as a starting point to discover something more advanced about how BigInt works.

Java translation!!

p.s. thanks for checking :)

Python, JavaScript, PHP:

Wrong array dimension in the describe block message, 'Simple 3x3 arrays' should be 'Simple 3x2 arrays'

At least javascript:

• Tests should fail without errors if the result is not an array.
• Tests should accept pairs [a,b] where a > b (descritpion explicitly says that 256 -> [[8,2],...] is valid).

In Python, the submission tests go up to 1000 while the description only states that inputs go to 500.

Depending on the tests in the other languages, either the description should be updated or the Python tests should be changed to match the description.

Lua translation!

python new test framework

I found the instructions very confusing.

I'd simplify it by saying that a good char is in the same column or row of buttons as the previous char.

I've got a Rust solution which failed the "num" crate check, since I used the div_floor function from there. Thought only num::BigInt was disallowed. No matter, I removed the dependency, and it still failed the crate check, so I removed all dependencies (itertools) and it still fails the crate check. I reset the environment with the button at the bottom, still fails. I don't know what to do now. Any ideas? I'm guessing the crate is still installed somewhere so the test is failing.

python new test framework is required. updated in this fork

In the PHP version, the random tests will occasionally pop up an empty string instead of a number, combined with an error:

Undefined array key ""

Stacktrace that is supplied with the code goes to the tests, not to the kata-code:

/workspace/default/tests/AddFunctionTest.php:68
/workspace/default/tests/AddFunctionTest.php:53
/workspace/default/tests/AddFunctionTest.php:145
/workspace/default/tests/AddFunctionTest.php:30

My code handles empty strings as zero, but the tests still fail, as an exception is thrown.

In PHP:

• No sample tests

• AssertSame should be used

• Usage of class and method is redundant and should be removed