Closed Ryman closed 7 years ago
r? @KodrAus
Specific review concerns:
cfg
stuffEncodable
makes any sense but it simplifies the imports and usage within this crate so hopefully it's not confusing for users?Still TODO if I get to it: more tests for serialization. This passes what we currently have but it's could be more exhaustive on our 'compatible types'. Any specific edge case suggestions would definitely be appreciated!
I think re-exporting both traits as the same name makes sense, since other libraries that only want to maintain one or the other can still satisfy the type bound by implementing rustc_serialize::Encodable
or serde::Serialize
(I'm pretty sure).
I'll pull this down to my nickel
branch and see how it all plays :) Looks good to me though!
What is the status of this? Waiting on anything?
Well this would need to be updated for serde 0.9
. Looking at this again I was going to test this branch in my nickel
PR. I did end up doing that, and it all worked out well. I didn't come back and report that though, so I think I dropped the ball.
I'd be happy to see it start moving again though.
It'd be great to have some movement on this. Especially considering rustc-serialize
is planned to be deprecated in 1.18: https://internals.rust-lang.org/t/rust-release-milestone-predictions/4591
FYI, I've been working on updating this to work with serde 1.0.
Closing in favor of #52
To use this feature, you can activate the serde feature:
The minimum compiler version for the serde feature will track stable.
Closes #33.