Repository navigation
v1.1.2
1.1.2 (2026-11-05)
This release stops mnavQuery_FindShortestPath from opening nodes past
its path length toward an end far away. No result changes for a caller
that keeps the contract.
Changed
mnavSetCorridor's documented failures no longer list a path whose
first or last point is not finite. A path's points lie in its
context's memory, and only the context's searches write them, so a
path handed back as the contract allows never has one. A path whose
points are an array of the caller's own is still refused with
mnav_errorInvalid. No result changes for a caller that keeps the
contract.
(#350)
Fixed
mnavQueryLimits.pathLengthpromises that no node is opened whose way
from the start and on to the end is longer, but
mnavQuery_FindShortestPathopened such nodes toward a finite end
past about 1e308 m. Its estimate of the way through an interval
overflowed to NaN there, and a NaN estimate passed the length test.
The estimate is now infinite for a root or end more than about 1e154 m
from the interval's end. That is pastMNAV_MAX_PATH_LENGTH, which
caps every search's length, so no node within a limit is turned away.
No result changes: the path given was already right.
(#354)