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.
Be careful when specifying the alphabet for the columns, because the letter "i" is omitted in the tests :)
Check the details section:
"For calculating the average point you may add your point to the given array!"
To my understanding that adding yourPoints is optional
The description says that you can:
"
rollback
User should be able to rollback a set amount of turns on the go board.
"
Accordingly, the rollback method takes one argument - the number of steps back. Which means to return the state of the board n moves back. This means that every movement on the board must preserve the previous state of the board in order to return to it if necessary.
For example, after movements for board 9x9, the result will be a board:
If the rollback method with argument 2 is called, the result will be a starting board:
I hope this clears something up?
p.s. Initially did not specify, I will add, that together with the rollback of the board, rollback should also be made for the order of the players' moves.
Nonsense, the kata is fun to the point when you start encountering weird ideas that author came up with to "spice" things up. Most ridiculous of which is something called "rollback", which I have no idea how it is supposed to work and description certainly does not clarify this. It has nothing to do with the game of Go and is total nonsense. Basically I have written the whole solution but cannot get it through random tests because idk what author had in mind.
Fun challenge but the instructions needs to be rewritten. There are several requirements that are never given in the instructions. I got halfway through only to find that I should be able to handle multiple move inputs at once. This really should be mentioned in the move section, its pretty important.
Hi
A question : why testing the state of the board with game.board instead of game.board(), the same for turn
IMHO , a method or function gives more freedom to implentation (it's encapsulation in fact) ,
Accessing directly to attributes creates a constraint : it fixes the type of attributes and /or implies permanent updating of them
This kata's description is ridiculously badly written. It is so frustrating to write the whole solution just to find out at the end that there is supposed to be a rollback functionality. The self capture move is not explained, some edge cases are not explained, important information does not get highlighted enough (letter I does not count etc.). This kata would be pretty fun to complete if not for this terrible explanation...
This kata should be updated from
Node 10.x
. It is one of the very last ( less than20
, realistically less than10
) to prevent removal of thatNode
version.Maybe not exactly an issue, but in java, the random tests appear to never place a stone on the top row. I'm assuming the RNG's upper bound is 1 lower than it is supposed to be. As far as I can tell, the game board's size is properly interpreted by the test engine
@rwood112 wait so is rollback(1) trivial? I was under the assumption that the argument for rollback denoted the number of moves to undo.
I'm currently in the same boat with java. Makes me wonder if theres an issue with the java test-checker.
Hey, how many random test assertions are there? I am getting a timeout on 29ish ;/ Also, how many ms did it take you to do in python?
Whose turn is it first and does placing handicap stones whose turn it is?
read the description:
Loading more items...