Wrapping would increase golfability

[sparr]

If the IP goes off the playing field, the program will terminate.

This aspect of the language surprised me, especially given that both the predecessor languages have wrapping.

Not having wrapping means that the three corner cells must have IP redirection instructions unless they are the last instruction of the program, and also requires edge cells to redirect the IP if it's not already traveling along the edge.

The README doesn't explicitly mention golfing as a goal or use for the language, so maybe I'm off base here, but so far that seems to be where the language is being used. Not wasting instructions on lack of wrapping would reduce golfing character counts in many use cases.

The only con is that it would require & in programs that don't already use it.

If there is interest in this change I could produce some example programs with and without wrapping to compare size and complexity.