Closed CharlesPublic closed 2 years ago
That's because those numbers are not exactly representable as floats, which is what FastPriorityQueue
uses for priorities. Try the GenericPriorityQueue
instead.
That's because those numbers are not exactly representable as floats, which is what
FastPriorityQueue
uses for priorities. Try theGenericPriorityQueue
instead.
This seems to be similar to the problem I'm experiencing and while using floats.
Hello BlueRaja,
i think i just found a bug in the FastPriorityQueue.
I enqueue 1 M entries, then dequeue 1 M entries, this works fine for the SimplePriorityQueue. But when i use the FastPriorityQueue then some of the dequeued Values come back in the wrong order.
Here is my test:
EDIT:
The Bug doesn't occur in SimplePriorityQueue The Bug doesn't occur in GenericPriorityQueue
The Bug occurs in StablePriorityQueue The Bug occurs in FastPriorityQueue
I've tested this both in debug and release mode.
I found many wrong results like:
wrong order at index 110 -2147090649, -2147089868, -2147082607, -2147082606, -2147068169 expected -2147090649, -2147089868, -2147082606, -2147082607, -2147068169 actual
Cheers