Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
Not a school 42 student here - I just switch to whichever loop I feel is appropriate.
Thank you for the kata, I just wanted to query whether there was a typo in the description. When describing
get_input
it says:However the rest of the description talks about the player pointing at a column, so should it be the following?:
Hi, sorry for not responding to your question sooner (I somehow missed the alert about it).
I've just added more detail in response to another question here, which hopefully answers your question.
This comment is hidden because it contains spoiler information about the solution
This comment is hidden because it contains spoiler information about the solution
This comment is hidden because it contains spoiler information about the solution
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.
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 :(
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.
Thanks!
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?
I enjoyed this one, thanks.
There's an interesting corner case you could potentially add -
"{{i}"
or"{{s}"
which I think a few of the existing solutions don't account for.Thank you, I think having the note right next to it too makes that part much clearer now.
Regarding units I was assuming SI units, but because of the comment I had assumed that D_WATTS was in Watts, not Watts per minute? (Still not 100% sure what the unit of DELTA_T is).
Loading more items...