Currently, the BucketOpenList does not support negative key values and can only
be used with evaluators that resolve to non-negative values.
As far as I see this, it is unlikely that it needs to be used with negative
values, but then it should warn if somebody tries to use it like this.
Alternatively, we could think about removing the bucket-based open list from the
trunk, because the map implementation is not significantly worse in the case of
unit action costs and in general better in the presence of action costs.
The third possibility would be to implement the support, which should not be a
big deal, either.
|