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.
Your solution is overwriting the namespace if it doesn't exist or doning nothing if it does. You need to create the namespace if it doesn't exist and always add the MyClass stuff.
This comment is hidden because it contains spoiler information about the solution
There is actually a test case failing, the very last one. interleave should be able to handle null being passed in as an argument. I'll see if I can get the description updated ...
That description does seem a little ambiguous, I've adjusted the documentation.
Could you post your code with a spoilers tag? It sounds like you have an index wrong somewhere, but I can't really tell without a look at your solution.
This comment is hidden because it contains spoiler information about the solution
That's actually a good idea, but implementing it would break all the current solutions. Hmm, I'll have to think about it little before make a change like that.
I'm also pretty sure there are bugs in the summation tracking ... What I get for writing code at 1 in the morning!
This comment is hidden because it contains spoiler information about the solution
That performance requirement is brutal! I have a version that tracks changes, but so far I'm only able to get about 600~700 iterations out of it!
I'm not sure if this is a feature request or a I need to be pointed at extra documentation. How would I test wether a kata solution can handle a particular global variable being defined or not being defined. For instance, the namespace kata I wrote a little while back, I would like solutions to work wether the global namespace is predefined or not, but I can't figure out how to test that.
You might be able to do what I'm looking for by wrapping the code under test in a closure that's callable in the test suite rather than just using a preload block ... not sure ...
Interesting, that's one I hadn't thought of. I'm trying to decide if your solution covers a case that should fail since it pollutes the namespace with an extraneous function ....
Ya know, I just wrote that and I have no idea how I messed it up so badly, fixed!
Take a look at the first example. The goal is to walk the 2d array in a spiral ... Which could definitely be said a little clearer than was done.
Incidentally, how does a kata move out of beta? I'm probably missing it, but I haven't seen anything documented ....
Loading more items...