That's an interesting situation you found. It's a strange thing to be testing without any corresponding specification - it has purpose but I think the test output should be phrased differently because that's bit of a red herring. If you print out your parameters a b c that should tell you enough to continue.

Because I have eluded capture so far...

If caged I would have to eat crow.

You push it to the top of the stack.

retired

Yay! Free points!

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

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

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

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.

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

Fixed!

Updated the description

I also missed that in the description

Thanks for your remark! The word consecutive has now been highlighted in the task description