It means you found a typo.

Fixed. Thanks.

fixed, thanks!

و الله 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)

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

Approved by someone

Hi,

Are you sure that the test case with { "" } is correct? It is not a null-terminated array, how are users expected to figure out where the array ends?

Thanks!

How does this look?

I generally prefer to not have branches on random bools at all. Just generate both variants, append them to a collection of test cases, shuffle the collection, and now you have one branch less in the code, and consistent ratio of both variants between runs.

awesome TIL

done

(and replaced the solution set-up return value from an int to a string)

thanks

I replaced the solution with yours as well

Kata retired.

fork