-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Use serde instead of rustc-serialize ? #18
Comments
The downside is you're limited to the nightly branch. Beyond that, I don't have a lot of knowledge about the differences :\ |
Ok thanks for the clarification! |
Just for reference, this is waiting for rust-lang/rust/issues/29597 and rust-lang/rust/issues/29644 to land in stable. |
I think it would be OK to make the jump now. Serde is becoming the defacto serialiser / deserialiser even though some ergonomic features are only available on nightly. I think there are 2 ways we can make it work:
Code gen is obviously more convenient but requires some extra work in the build script. Which is not a big deal. |
I followed the serde readme and made an experiment in this branch, refactoring only Although it works, the build time has become quite long, 1.5 mins instead of 9 secs. With codegen:
while before:
I didn't PR because I think it's not worth the long feedback time while working. The feature tickets are apparently being worked on, I suggest waiting until they arrive in the stable release. |
That is a reasonable choice, thanks for looking into it :) |
@gambhiro that doesn't seem like a fair comparison because you are not including any of the other dependencies. On my computer a build following |
@dtolnay Thanks for explaining. I'm quite new to the rust build tools. |
I have heard good things about serde. At the moment I use rustc-serialize, should I use serde instead?
What are the differences?
The text was updated successfully, but these errors were encountered: