vspiliop / martian-robots Goto Github PK

OO design but with a functional twist :-)

• Keep method signatures clear: Refactored to use the Either and Try monads of Vavr to avoid throwing exceptions.
• All possible errors are handled via Either composition.
• Object Oriented design for the Robot, MarsSurface, Orientation and Cartesian Coordinates.
• For MarsSurface a purely functional and immutable HashSet is used from Vavr.
• Robot, MarsSurface, Orientation and Cartesian Coordinates are immutable and threadsafe.
• Models an instruction as a Function that takes a Robot (or in case of an already failed execution of a previous instruction, an IllegalArgumentException) and returns a new Robot or an IllegalArgumentException, if the current executing command failed or a previous one did.
• Specifically, an instruction is defined as Function<Either<IllegalArgumentException, Robot>, Either<IllegalArgumentException, Robot>>.
• InstructionChain are chained such instructions via andThen().

The surface of Mars can be modelled by a rectangular grid around which robots are able to move according to instructions provided from Earth. You are to write a program that determines each sequence of robot positions and reports the final position of the robot. A robot position consists of a grid coordinate (a pair of integers: x-coordinate followed by y-coordinate) and an orientation (N, S, E, W for north, south, east, and west). A robot instruction is a string of the letters “L”, “R”, and “F” which represent, respectively, the instructions:

• Left: the robot turns left 90 degrees and remains on the current grid point.
• Right: the robot turns right 90 degrees and remains on the current grid point.
• Forward: the robot moves forward one grid point in the direction of the current orientation and maintains the same orientation.

The direction North corresponds to the direction from grid point (x, y) to grid point (x, y+1). There is also a possibility that additional command types may be required in the future and provision should be made for this.

Since the grid is rectangular and bounded (...yes Mars is a strange planet), a robot that moves “off” an edge of the grid is lost forever. However, lost robots leave a robot “scent” that prohibits future robots from dropping off the world at the same grid point. The scent is left at the last grid position the robot occupied before disappearing over the edge. An instruction to move “off” the world from a grid point from which a robot has been previously lost is simply ignored by the current robot.

The first line of input is the upper-right coordinates of the rectangular world, the lower-left coordinates are assumed to be 0, 0.

The remaining input consists of a sequence of robot positions and instructions (two lines per robot). A position consists of two integers specifying the initial coordinates of the robot and an orientation (N, S, E, W), all separated by whitespace on one line. A robot instruction is a string of the letters “L”, “R”, and “F” on one line.

Each robot is processed sequentially, i.e., finishes executing the robot instructions before the next robot begins execution.

The maximum value for any coordinate is 50.

All instruction strings will be less than 100 characters in length.

For each robot position/instruction in the input, the output should indicate the final grid position and orientation of the robot. If a robot falls off the edge of the grid the word “LOST” should be printed after the position and orientation.

5 3
1 1 E
RFRFRFRF

3 2 N
FRRFLLFFRRFLL

0 3 W
LLFFFLFLFL

1 1 E
3 3 N LOST
2 3 S

Install Lombok plugin. This is not required if you use maven to build and test.

• Install Java 11 or above
• Install Maven
• Run

 mvn clean package

• Update instructions_from_exercise_description file to set any input instructions.
• Update expected_output_from_exercise_description to set any expected results.
• Run the specific unit test via maven

mvn -Dtest=ProcessingAStreamOfCommands test