The current moveTo implementation doesn't support things like multiple targets, flee, etc.
Let's start with a basic improved moveTo that supports those additional options.
We should configure (at the library level) the caching strategy - either in heap, memory, or in a memory segment - for paths. This is mostly a precursor to being able to configure caching for other kinds of data - one-off paths will almost always be better cached in heap.
The current moveTo implementation doesn't support things like multiple targets, flee, etc.
Let's start with a basic improved moveTo that supports those additional options.
We should configure (at the library level) the caching strategy - either in heap, memory, or in a memory segment - for paths. This is mostly a precursor to being able to configure caching for other kinds of data - one-off paths will almost always be better cached in heap.