I've even approved a translation on that one, haha! I'll "retire" this kata.

But it does interfere with native behaviour ( for .. in ). Non-enumerability should be specified and tested.

I think it's a unique enough problem without those hints.

Gah, fixed! ;-)

Good point, I've added a relevant example in the Kata description and sample tests and mentioned that the digit should be returned "as an integer".

( JS )

indents in test suite ( random tests part ) are not correct. this is not optimally maintainable. please follow CW Coding Guidelines. ( you may have mixed spaces and tabs. )

I found out the digits are encoded as base-10 numbers. This is not very intuitive, given the explicit "digit" in the title. It's a valid ( and perfectly reasonable ) choice! but specify it explicitly.

Also, the ( JS ) Example tests did not even make it clear. Consider adding a test that showcases this spec.

How is the last digit to be encoded, especially for bases over 36 ? I could probably glean this from the example tests, but it should be specified in the description.

duplicate of this issue

I've bumped the number of random assertions up to 100 per category (small, larger, largest), feel free to inform me if more assertions are required :-)

Whoops, fixed! ;-)

I think you need more random test cases. My solution appears not be correct all of the time, yet I was able to pass random tests on second attempt.

shouldn't the second constraint be on d, not n ?