The other kata is now available

Fixed

Either could have worked. Approved with 2D array.

A string is ( with the right encoding ) isomorphic with a 2D array of characters, so this suggestion would not materially change the kata.
Doing or not doing this is just a design choice, there is no right or wrong there.

"even if the targeted enemy has been killed by a previous (in the alphabetic order) turret, the shot is counted"
Don't understand( Could you clarify please?

fïxed

mmhm, perhaps :)

Could be another kata...?

I also think you enjoy generating these gravestones ;)

Yeah. To confuse the devil.

disallowing recursive implementations because the function you require contains the word sort

this is easy enough to work around of course. but it's very, very user-unfriendly to enforce the restrictions this way.

there should also have been a separate test block enforcing the restrictions with normal test failures, instead of the fugly exceptions that are being raised in the course of functionality testing.

ETA: sort_array = sorted, which is a valid solution apart from the restrictions, raises the following exception:

TypeError: don't know how to disassemble builtin_function_or_method objects

that's apparently a test error, not a code error. that's just one ( but very bad ) way in which the restrictions enforcement absolutely s*cks.

unrelated, but I'll mention it here because the kata is retired anyway: there is absolutely no reason to use a fscking BubbleSort as the reference solution. you could just have used the native sort - it's not forbidden from testing!

but kata depending on forbidding native methods are almost always a bad idea anyway ( which you had been told ).

modules forbidder.

• wouldn't be enough, especially in a case like this
• the kata is already retired

done

Already added by somebody.