Yes i saw it after i posted. thanks

Yes, it's normal for a Draft.

Ruby 3.0 should be enabled, read this to learn how to do it

Please organize the structure of test fixture as following (although it has been mentioned in the attached link, I'm repeated here again)

describe "<This message should describe the categories of test groups inside this block>" do
  it "<A short message describing this test group>" do
    expect(...).to eq(...) #Assertions
    #Or Test.assert_equals(user_response, reference_response)
  end
end

My opinion is that anyone can write a kata that is challenging as a result of poor instructions, but that it takes someone of a higher standards to write challenging kata with clear and simple instructions. I agree with your assessment, and thank you for the alternative links.

That's not an issue, more of a "I don't like this kata's format".

Besides, there are already many such katas: https://www.codewars.com/kata/multi-line-task-plus-plus-hello-world and https://www.codewars.com/kata/multi-line-task-hello-world

You're hitting the recursion limit.

What language are you using?

Apparently, voters feel you can have either a normal or a code golf kata, but not both. The fact that some people feel a need to golf normal kata doesn't help of course.

Myjinxin sometimes used to have both versions where you could not submit golfed ( or at least too-short ) solutions to the normal version. That requires advance planning of course, but it might be a solution to this problem. Too late for this one, but maybe for next time?

Closing now.

I don't think it's fair to retire a kata just because people can cheat. In that case, almost every kata would be taken down because people could just google the answers. People who cheat on cw are just cheating themselves, it shouldn't have to affect the kata.

Issue can't be solved. Your issue is pointless.

If you want to have a discussion wether or not this kata has a right to live, I don't think raising an issue is the right way to do it. I really don't think raising perpetual issues is the way to do it.

The only 4 people who solved it so far have done exactly that, hehe.

Issue below is still present. This kata is pointless.

Are you sure about that ?!? ( Yeah, I had to take off the const at the start .. )

Well, i cant really fix that :( . Even so, i dont think anyone has posted a 61 char or less solution on the original