-
-
Notifications
You must be signed in to change notification settings - Fork 774
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
MessagePack support #96
Comments
That would be wonderful! If you haven't starting working on it yet, I think I have a partially implemented version I started and didn't finish months ago. |
I am working on that. It seems to work pretty well except for enums which are very complicated as each variant can have a different type. How should I publish the code? |
Actually I've already have The real challenge - is to how implement zero-copy deserialization into a non-owning structs, which contains Personally I want to make PR is ok if only |
My main problem with rmp, mpack and msgpack was that neither of them allowed me to serialize [u8] to msgpack bin. Instead all rustc-serialize based serializers serialize [u8] as a list of single u8 which is very inefficient as half of those bytes require two bytes to serialize. |
Wrong: https://github.com/3Hren/msgpack-rust/blob/master/src/encode.rs#L646
UPD: If you have problems with RMP you should definitely create an issue :) |
Yes, you are right. However I did not figure out any way to use that with rustc-serialize. |
With |
Not exactly but there is a wrapper type |
@3Hren and @dswd: I've also hacked up msgpack support in 3Hren/msgpack-rust#26. |
This has landed in rmp! |
I don't see how this improves on the |
Does this help with deserializing: 3Hren/msgpack-rust@380a68b? |
And this should help with serialization: 3Hren/msgpack-rust@6c1f7c1 |
Update num-macros to rust master
Does anyone need MessagePack support?
I can implement it in https://github.com/3Hren/msgpack-rust as an option.
It's not an issue actually, but it may generate issues if I start to working with it :)
The text was updated successfully, but these errors were encountered: