This was my first kata solved, i spent a few hours learning the maths to understand what i am supposed to do. But after that it was easy. Thanks for the challenge.

You push it to the top of the stack.

retired

Yay! Free points!

This description, I'm lost for words ... So much noise, and yet so little information provided. I am left with more questions than answers after reading the spec. You talk about 'when this happens, then ..', but never mention the trigger for the 'when' part. The order in which actions are to be performed, is also lost on me. And where does this magic number 12 come from? Is this the quantity for a full yard/pile? Why isn't this anywhere in the description? I'm truely amazed how you fucked up a (probably) good kata, with such a low quality description.

same problem ,i will try my best to find a solution.

Yeah, there's something weird going on in that 6000-6200 range. I still haven't really figured it out. [shrug emoji]

can't even do the hard code part -_-

You are not alone, you are not alone ...
:-)

I passed it with some hard-coding. Shame on me. I still don't understand when to go high or low in the range of 6000-6200. I'll go back and train again, trying again to figure it out and solve it more honestly. (In my defense, I planned to only hard-code until I discovered the pattern or rule. But I'm still working on that... )

I think most people will assume that the operations "consume" their inputs, and they would be right. But yeah, the description should state it anyway, just to be clear.

What happens to the result of the add, sub, mul, and div operations? Specifically: Is the result pushed onto the stack as a new top value, or does it change the value of the current top value on the stack? This isn't clear from the description or the example.

I see what you mean. I am initializing the total of the ascii values to 0, so if there's no input, that zero never increases and eventually gets converted to a space. So if there's nothing but that space, I should return an empty string. Otherwise, spaces resulting from zeros should remain in the result.

I think you've read that failure message wrong, it's mildly confusing (cause it's making an attempt at showing it inlined in the message but it just comes out as badly spaced and it doesn't tell you it's doing it, when it could simply use a string literal), and you're looking at a space in the converted string, not the input.

Return a empty string if the input is empty

(an btw)

I don't see why there's a need for that special case though. SPECIAL case, not edge case, because that's not included in the rules section.

... I also don't understand why "printable" or cp1252 are mentioned, and I find the wording "space and other printable characters" really strange as space arguably is not printable and then one may wonder what else that kinda isn't printable might show up. except, none of it matters anyway