Please add more test cases, especially random tests.

Please fork and re-publish your translation. Cannot approve because there are some merge conflicts.

Please fork and re-publish your translation. Cannot approve because there are some merge conflicts.

Please fork and re-publish your translation. Cannot approve because there are some merge conflicts.

Please fork and re-publish your translation. Cannot approve because there are some merge conflicts.

Dont know. System tells me there are recent changes from related record.

Suggestion: Fork your solution and re-publish it.

Cannot approve because there are some open merges. Please merge your translation with recent changes. Thanks.

Don't forget: Each declared variable needs space in memory (stack or heap). In this kata, you might use three different vars but in real life projects with millions of code and thousands of vars, that solution might be best practise (depends on your team and the concrete project / requirements).

Sounds good. In general, I agree with your opinion. One should write code in a safety way, i.e. check each input and don't make any assumptions. Double-checking is better than getting an exception (or much worse: Having a security issue).

I'm afraid I have to disagree. The reason is very simple: What is a "best practise"? Answer: It the best solution which solve the requirement / the problem.

According to the task discription, the array has only numbers and at least one element. Why should we write boilerplate code? Why should we write any checks for situations that never occur?
The consequence of your idea would be that you get code which is not good readable and maintainable.

Python Translation available, please add it.

what is human readable format? example?

@SegfaultZ: This is a join of two tables. I don't know what you saw.

This is not ANSI-SQL, but there is no requirement to use ANSI-SQL only.