Okay, here you go, hit it while it's fresh! ;)

Hi David, all points have been addressed. Please let me know if you have further questions or need any adjustments, thanks.

Fixed, sorry for these mistakes. Mutation should be tested now, also copied your tests, grouped by length 10, 100, 1000, 10000.
Want to ask, do kata description is same on every language? Because if it isn't, maybe it's better to name lists as Go slices.

For reference, in Rust both the method signature and the input variable would have to be marked as mut.

fn mirror(list: &mut [i32]) -> Vec<i32> { /* etc */ }

assert_eq!(mirror(&mut []), &[]);

In Rust almost anything can be mutable, but it's opt-in and has stringent borrow rules.

Hum, interesting. I've only run into that once!

Does this forked version work? I noticed it had a merge conflict in the description due to a newline before "More info".

By that I mean is it unnecessary to check for input mutation?

Correct, they explicitly need to be declared as mutable. There's no need for .slice() in JavaScript or similar ways to avoid mutation of the input.

Thank you for taking a look.

Fixed the typo.

The reason I removed the language-specific code block is:

• it's a really simple task, so there is nothing language-specific in it;
• if/when the kata is translated in multiple languages, you end up with 5-10-15 very similar code blocks, which can potentially cause issues when approving translations (a.k.a description merge hell)

But if you want, I will restore it as you like, no problem ;-)

It's not possible in prolog. Any operation on a list creates a new list (AFAIK).

You kata is very well.
Recently I also began to create katas and paid attention, that after the kata has been just published, the downwoters gather to sink it.
However in a few days, the votes get better and better.
I wish you good luck and hope your kata will be approved soon.

What's the point? Here is the same solution without numpy, and it's faster as well.

Thanks for the suggestion, I would ammend the description to say to leave underscores in the string as it is, but the kata has been retired.

See here.

There's not much point in combining two existing 8 kyu tasks into yet another easy kata.

I don't think an 8 kyu kata has been published for over a year. Your kata isn't bad, it's just that people tend to vote down unless thay find the kata novel/interesting.

There're already hundreds of such small katas where you have to use 1-2 built-in features, including solely sorting or reversing a list. There's not much point in having more katas simply combining 2 8 kyu tasks into another 8-7 kyu task, so, obviously, PU's will mostly downvote this.