1
Vote

Optimize Move()

description

Right now the Move() method in ExecutionContext is horrible. It goes through the FungeSpace one cell at a time, so if the next instruction is 1000 points away ... well, that sucks. Need to come up with a way to not only find out the next valid cell in the current direction, but also cache those values as cell references to remove the need for more lookups.

comments