Java translation, please review.

Python new test framework should be used (Refer this for more detail)

C translation

Sortable does not really define a sorting: at the very least a sorting algorithm should accept an input list, a comparison function, and do the sorting.

However, the current design has none of these: it instead have algorithms that call certain functions in certain ways, and asks us to distinguish between their call patterns. This isn't sorting at all: in fact there are no "input" to begin with because list access/write are all done inside the user-defined functions (SortDataType.arr is completely irrelevant). They are not correct sorts unless user code obeys the constraints stated by the interface.

Sometimes actual test crashes:

Caused by:
  process didn't exit successfully: `/workspace/target/debug/deps/challenge-07bd72047d917620 --show-output -Z unstable-options --format json` (signal: 11, SIGSEGV: invalid memory reference)

I have the correct code, although I cannot get to work fast enough to complete more than 33 test cases..

Any reasons why the input is always given in an ascending order? None of the solutions actually require this.