I suggest specifying how to sort if the sort key is not unique. I got this random test:

Expected: [[[99, [58, 39], 31, 19], 40, 3], 85, 46, [27, [17], 2], 2]

But was: [[[99, [58, 39], 31, 19], 40, 3], 85, [27, [17], 2], 46, 2]

Scala translation

Prolog translation

C++ Translation

Java translation

Shell Translation

In JS (at least):

This solution utilizes a special character in a way such that if that char was present in the input string, the code would fail.

Complete testing should include all special characters to defeat solutions of this catagory.

• Description should be language-agnostic

• Should give example tests for capital letters

Any way to print something in nasm ? Got segmentation errors on the random tests but i'm unable to reproduce them in my own test cases

Missing corresponding imports in Python for real and sample tests

A bunch of issues in R translation (detected by Pluue):

• Random tests pass in tables of single-letter strings instead of strings.
• return FALSE passes all random tests.
• return TRUE passes all performance tests.

"All column titles will be uppercase."

This isn't true, PHP random tests include all sorts of strings (and also expect a valid result from them)

string(4) "Kzu8"
Failed asserting that 211450 matches expected 233914.
Expected: 233914
Actual : 211450