• the return value is a function of the input's length and can potentially be as large as it, so the return type should be the same as well: size_t
• i don't like that there are no assertions run at all if the solution is correct. i think this abuses an implementation detail of Codewars' runner, namely that a tests group associated with no assertions will always succeed. the guard

  if(submitted != expected) {
  

  is not needed, in my opinion.

C Translation (user somewhat inactive).

You should not post methods / code / solutions without using the spoiler flag, or else anyone can see it. I have added the flag to your comment.

but it's a palindrome...

When you observe the error feedback it tells you that your function returns NaN, so you should start debugging with console to see what is what and why that happens in the first place.

Specifically, look at what lastIndex amounts to, and what results from that.

Good luck!

First of all, please do not post as an issue when you do not know why your code does not pass. That's reserved for when there's a problem with the kata code and you can give examples as to why. Instead, post as a question.

how does the tester expected them to be spelled?

that would be a world better than expecting to one day have literally dozens of near duplicate kata

fixed in the last version

solved

Fork

• JS random tests rewritten

I unpublished the kata because it lacks random tests.

Random tests are necessary for almost every Codewars challenge. Consuld Codewars documentation (Python authoring guide, authoring guidelines), authoring examples kata, or #help-author channel on Codewars Discord if you need help.

No Random Tests

Please don't reinvent testing. Test function return values instead of capturing console output. This way, when tests fail, there is no debug output.

Read documentation and test suites of kata you've solved. Also, ask Discord#kata-ideas whether or not this is a duplicate.

Duplicate?