No. It's your code's problem.

Next time raise your question as a question and not an issue when you have one.

There's a bug in your code. It should be quite obvious if you look at that failed test case properly, so it's left for you as an exercise ;-)

(Also, can people stop being so condescending as if they're 100% sure it's the kata's fault? Because in like 90% of the case it's the contrary, which "my working code cannot pass your tests" is seldom one. Also, most of these "issue" comments are unhelpful to anyone who's trying to resolve any possible issues.)

I do agree with you that this isn't best practice. However, "Clever" is, according to CW, a code that you wouldn't necessarily use in production. In fact, I refactored this one to this

When I write code here, I let myself go, without worrying about readability much. And I think I'm not the only one ;)

this is not a best practice, the code is not very readable, I used to think the shortest answers were the most clever but try working on a whole program written like this, you'd struggle to find out what it's doing...

instructions wanted you to use regular expression btw

instructions wanted you to use regular expression btw

you need to optomize your code more, I had to litereally re-do the same code 4 times before it worked but the learning experience was great, i'm more cognizant of what works best for efficiency than before. It took me ages but eventually I got it. I suggest take a break then come back to it the next day, thats how I got new ideas.

this is def not 6kyu... should be 8 or 7.5 :)