-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
serde failing with non-primitive items #4
Comments
This test fails also using a standard HashMap in place of the PriorityQueue. |
@ckaran can I use the modified version of your code to fill an issue directly to serde? |
@garro95 My apologies for not replying sooner, I've been in and out sick for a bit. As for using my code, please, go ahead! Anything that can help fix things is good! Do you want me to create a pull request that converts the code into a unit test? Even if the problem is in serde, it affects your code as well, so have a test that catches the bug will be useful. BTW, did you file a bug against serde for this? They really need to know about it. If you want to use my code as a basis for the bug, go ahead. |
The bug was fixed and I used your code in unit tests. I told the serde guys of the bug in a IRC chat that we had. |
@garro95 Thank you for fixing the bug! |
I've been testing priority-queue for use in a home grown simulator framework. One of the things I need is for the queue and its contents to be serializeable via serde. When I test priority-queue using primitive types for the items, this works, but if I test using non-primitive types for the items, I get a the error string
thread 'main' panicked at 'called Result::unwrap() on an Err value: ErrorImpl { code: KeyMustBeAString, line: 0, column: 0 }', src/libcore/result.rs:906:4
. The following code should illustrate the problem; look in the area under theFAILING
block.The text was updated successfully, but these errors were encountered: