Please remove the requirement for returning undefined. The C# version does away with it, for the better. It adds little to the Kata and instead makes translating the task more inconvenient.

nice

Also this one: https://www.codewars.com/kata/5a02a758ffe75f8da5000030

Damn, I find the current kata the best quality of those 3. I don't know how to proceed. Leave this one in beta, or start a deduplication process ..

I believe this kata is more interesting and has better quality as an earlier approved kata (with low satisfaction rating): https://www.codewars.com/kata/527f782024b930114700076e.

I would approve this one, and on deduplication get the other one retired.

Euclid would be proud of you :D

My main concern is that solutions of this kata are not substantially different from existing approved Hanoi Tower katas. So I propose to introduce a new requirement which makes this kata more challenging and different from already approved katas. This new requirement will invalidate all existing solutions but it is fine for an old beta kata with a few solutions.

I only see this now, no longer get much notifications around here. Is there a type of current solutions you would like to see invalidated by introducing this new parameter?

Here is my idea: Add a new parameter start. The task is to return solution steps starting from the given step start (and with the given number of disks). For example:

const tower = hanoi(3, 1);
tower.nextStep() // returns [[3], [2], [1]]
tower.nextStep() // returns [[3], [1, 2], []]

Do you think it is a good idea?

Give me a week to remember what I was going to add to this kata and to implement new requirements.

Also, this kata adds progess indication and lazyiness to the task.

Any news on this, or should we go ahead with approval?

Compilations tests should be added for cases like calc.One.One.One or calc.One.Plus.Plus.Times

duplicate issue