It means you found a typo.

Fixed. Thanks.

Locally you're not using the same input from the tests, not a kata issue.

lines = ["CAT"]
rotors = [[1,13,27]]
result = ["DOG"]

In your code, with that input value before + rotors[i] makes no sense, before is a number and rotors[i] is either an array or undefined depending on i value.

rotors // array of array-of-rotor-values. Each array-of-rotor-values is applied to the corresponding display line

Consider a flap display with 3 rotors and one 1 line

what does "one 1" mean here ?

approved

fixed, thanks!

approved

thanks for your efforts

in the Test Cases, maximize_points() is still declared as returning unsigned

و الله do not rember the reason for malloc.h as it was six years ago...

And there is no blind following...
As it seems reasonable to add empty strings (at least for one argument) because it is a 4kyu kata!

But anyway i do think there should be a consensus on throwing away empty strings in all languages or editing the description to include them (not just my or your opinion)!

• return type altered
• tester adapted (this translation was from before I had created my helper function stringer)

Hello, thanks for considering the changes. I am not criticizing your work in any way.

Following the original version blindly is not a hard requirement on Codewars. When it errs, you do not have to carry it over in your own translation. An empty string is not an usual representation of 0, and there are many complaints about them in the Discourse (here is the open issue for C with 17 likes).

About malloc.h, I would be curious to hear about the technical reason behind its inclusion ?

Definitely, there was some reason for including malloc.h instead of stdlib.h
and probably you should have to wait for another six years before noting that...

Despite the reason Updated to include stdlib.h instead of malloc.h

Added the case with empty string to Sample Test to inform users that there can be such cases to be compliant with the original version!

Edit: though may be i should not do it because another languages do not inform of such cases!
So i will remove it from Sample Test

• 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.

also, the fixed test with an empty string is against the specifications and should be removed

#include <malloc.h> is not a standard C header. can you replace it with #include <stdlib.h> in the initial code ?