Temporary serde dependency fix

[reneeichhorn]

As stated in #55 #56 builds are failing right now because of an update of serde.

[larsbergstrom]

r? @TyOverby

Sorry to be pushy, but broken bincode on nightly is causing rippling CI failures across the entirety of Servo's dependency chain that uses it (many, many modules) and prevents us from landing any new PRs in those components. Thanks!

[tikue]

Shouldn't ^0.6 already prevent 0.7 from being used?

[reneeichhorn]

@tikue I think ^ allows minor version updates. At least it's compiling now for me when I use my fork as dependency instead of directly bincode

[tikue]

I could be wrong, but I thought only when it's not a semver breaking
update, and for versions less than 0, 0.X => 0.Y is breaking but 0.X.Y =>
0.X.Z is not breaking.

If that's the case, my best guess for what's happening is that the version
on crates.io was published before the caret restriction was added.
On Feb 28, 2016 2:06 PM, "Rene Eichhorn" notifications@github.com wrote:

@tikue https://github.com/tikue I think ^ allows minor version updates.

—
Reply to this email directly or view it on GitHub
#57 (comment).

[TyOverby]

I'll get on this. Do the tests work for you or is the CI broken?

[tikue]

Tests are mostly fine, all visit_* methods on Serialize/Deserialize impls
change to serialize__/Deserialize__ respectively. About 100 LOC diff.
On Feb 29, 2016 9:32 AM, "Ty Overby" notifications@github.com wrote:

I'll get on this. Do the tests work for you or is the CI broken?

—
Reply to this email directly or view it on GitHub
#57 (comment).

[TyOverby]

I needed to update a few more things in the Cargo.toml, so I made this change and committed it.

[larsbergstrom]

@TyOverby Thanks a ton!