Please allow results with or without initial (0,0).

( JS )

Function.prototype.toString should be nuked altogether in Preloaded.

Just setting _checker.toString to something leaves the door open for Function.prototype.toString.call(_checker), which still reads the source code.

C translation

• Rust translation
• Go translation

Description says: "Range of possible inputs: 0 <=len(l1), len(l2) <= 125000"
In JS in Turbo Large Range I got lists with over 190000 elements

Looks like a duplicate to me.

Having multiple output types is a bad practice.

The reference solution is terribly slow.

• All values can be calculated exactly
• Output type should be changed to something more reasonable

It's not very nice to publish the same kata with the same issues again, you know.

Output type should be changed to something more reasonable.

https://leetcode.com/problems/strong-password-checker/ ?

• The function name should be in snake_case
• The reference solution is broken
• This is definitely a duplicate, as pointed out below

With strings containing only one letter, random tests expect that letter to be replaced by a 0, not conforming to the description.

Testing for reverseOnlyLetters(<g)
'<g' should equal '<0'

Testing for reverseOnlyLetters(}~/$ (#H)
'}~/$ (#H' should equal '}~/$ (#0'

Testing for reverseOnlyLetters(o/&!)
'o/&!' should equal '0/&!'

A duplicate of this kata.

Strings of length 1 or less are not valid. Spaces are allowed in the input, but they should be stripped before checking. All other non-digit characters are disallowed.

None of this seems to be checked in the test cases (except for spaces, but even then it's always the same format). You might want to add test cases with malformed inputs, or at least different lengths/spacings.