it gets timed out in JavaScript with numbers that have basesuch as 1000000001
any help?

So, in the rust version, I think I've found an issue.

In the tricky_tests, sometimes I get errors like:

With n = 18283961446061854279
Expected 18283961446061854278 but got 138 at src/lib.rs:57:9

The problem is that, as far as I've tested, in Rust and Python, 18283961446061854279 in base-138 is 1111111111.
I've collected a few of these. They were:

17126426820319058418 base-137
15705261201683973613 base-83
17393337673075145131 base-254
18412318490320479416 base-565
17948489581465697281 base-255
18283961446061854279 base-138

I have managed to submit my answer, because sometimes the tests don't use any number that breaks.

Ruby translation kumited -- please check and approve

The description should specify a range for n even in languages where all numbers are safe.

The user can modify the input.

Reimplementing sort is a duplicate to many katas.

Test.assertEquals should be used in the sample test cases as well, please, not just the solution evaluation.

Sample tests are wrong.

Stable sort is not required by the JS specifications. In fact V8 doesn't do this at all.

• Duplicate, e.g https://www.codewars.com/kata/convert-to-binary
• Anti-cheat tests are too weak

Almost a duplicate:
https://www.codewars.com/kata/multiplying-numbers-as-strings

Why are we asked to multiply 2 numbers and the expected results are strings?