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.
Fixed the first thing, gonna work on random tests.
I don't know why it did that two times
Changed the definition of equivalent. Now it's both: same winnable lines, same turn. Two boards with the same winnable lines and different turns are not same in terms of gameplay, because the initiative is in different hands (winnable lines may change in a different way on the next move for different turns, which is not what I wanted from this kata initially).
Changed the definition of equivalent. Now it's both: same winnable lines, same turn. Two boards with the same winnable lines and different turns are not same in terms of gameplay, because the initiative is in different hands (winnable lines may change in a different way on the next move for different turns, which is not what I wanted from this kata initially).
Done
The input should be specified. Mention it's structure, and also define what is meant by 0, 1, and 2.
same too! easy
Great, I took the same approach
For anyone confused by this, read the comments that are pre-loaded in the solution box (where you write your code).
I realize these comments are quite old, but @DworkinFromChaos is right.
Specifications don't belong in the (mutable!) fields of the kata. They should be in the description, perhaps especially in the case where they cause otherwise working solutions to fail.
Isn't @paraliterary's point that the field is invalid but your solution returns
True
indicating that it is valid?Honestly this really stunmped me. What technique did you use here?
This comment is hidden because it contains spoiler information about the solution
I found your objection here confusing until I thought about it.
Fundamentally, I agree. However, I think the underlying problem isn't the logic of planets leaving the system. That's a symptom. The problem is that the orbits change. As you note, if a planet leaves the system on the left, all other planets shift to fill lower orbits. However, if a planet is destroyed the same thing happens. The logic is consistent and solvable, but it's weird. There's a sort of extra movement built into it.
My biggest complaint, I think, is that the series didn't build upon itself. It would have been great if each new entry in the series added instead of being essentially the same with a different skin.
Loading more items...