Confirm

Fun but manipulating element positions in slice is kinda pain t the ass for Go =)

Great kata. Very entertaining to solve. But i think it better fit 4 ku because of complication and some specific algorithm requirements

Seems that 4ku will better suit this kata because of strict performance restrictions

Good for OOP understanding and mastery lang syntax, but i think it's a little bit easy for 5ku

This is one of those problems, where solving is possible only with one specific algorithm

I think, there is no "clever" solution, only implimentations with brainDuck dependenses =)

Ok. I count this as solved, becouse basic test cases doesen't clearly represent some exceptions in full tests

Great Kata. The first where i need to think not only about solution but about performance.

I count this Kata as passed, bc i can't win another 1 or 2 seconds of perfomance, but my script works well in VC an do the job