Optimization for moving

[giovanichaves]

Why not just using currentCoordinates = positionAfterMove instead of calculating it again?

MarsRover/src/com/thoughtworks/rover/MarsRover.java

Line 48 in 4aec376

currentCoordinates = currentCoordinates.newCoordinatesFor(currentDirection.stepSizeForXAxis(), currentDirection.stepSizeForYAxis());

[priyaaank]

Thanks. You might be right, I am going to check if newCoordinatesForStepSize and newCoordinatesFor methods are redundant. Cause I have long lost the context of the problem, and now they look redundant.

I'll try to substitute and run the tests and see if it continues to behave as expected.

Cheers