You are right, I found the error in my numbering of array elements. Thanks for comment.
I'm afraid I can't remember the issue completely any more, but I believe it wasn't something that broke the kata, I was just pointing out bad memory management practice (hence it being a suggestion and not an issue). It's unlikely this would be the cause of your error, sorry.
My solution fails Attempt at 4th test, with error "Test Crashed Caught unexpected signal: SIGSEGV (11). Invalid memory access". Is the issue likely to be with my code, or could it be caused by memory leak mentioned in this thread?
Hey @FastestCoderOnEarth, sorry I've not really been looking at any CodeWars stuff for a while so there's not been any progression from my side here :(
@Greatlemer, what is your status on this one?
@Greatlemer, sadly there's not so much progress here from anyone.
Thanks for the comment, Greatlemer. Because the description mentions nothing about them, I have prevented random tests from producing leading zeroes any further.
For C at least, some of the random inputs have leading zeroes, yet the output's not allowed to have leading zeroes.
For clarity could something be added to the description to mention this requirement (that they should be removed), then some fixed tests added for it, so it's always checked?
Alternatively the tests should not produce inputs with leading zeroes.
Taken care of.
Perfect, thank you!
There are a bunch of noisy compiler warnings coming from the predefined section in C. It would be nice if these could be fixed as it makes it a little harder to debug otherwise.
On the C version the random tests gave me a date within the omitted period (Sep 3-13 1752) - what is the expected behaviour supposed to be for that range?