-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Priority not persisted after enqueuing #63
Comments
I'm not able to reproduce this issue. Specifically, I added this unit test, which passes
Less importantly, using a custom node class that extends |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using a
SimplePriorityQueue<TItem, TPriority>
, whereTItem : GenericPriorityQueueNode<TPriority>
andTPriority : IComparable<TPriority>
; i.e., my Node class is derived fromGenericPriorityQueueNode
and uses a custom struct as the priority.The prioritization seems to work correctly. But immediately after calling
.Enqueue(item, priority)
, thePriority
property of the queued item iis set to the default value, instead of the valuepriority
which was passed toEnqueue
.Have I misunderstood how to use these objects? I'm implementing D* and was hoping to get the Key value from the
Priority
property.Minimal working example (included the whole
Key
struct in case it's important):The text was updated successfully, but these errors were encountered: