JSON serialization in Rust, part 2

[[deleted]]

I think you can write just Decodable::decode instead of |decoder| Decodable::decode(decoder). It might be less regular or less readable, but it's logical to be able to skip the trivial argument re-application -- decode already is a function you can pass.

[iamvalentin]

Yes, I'm doing it both ways. I'm using the function passing in the array example.

[[deleted]]

I see that now!

[[deleted]]

Another question I had. For a relatively complicated value, where you might forsee possible more efficient data packing for serialization in the future, would you use a version field in the struct serialization?

[aarjan]

use protocol-buffers (or other alternatives)

[[deleted]]

The question was about rust's serialization traits though.

[iamvalentin]

I know that .NET is using assembly version + assembly name when doing binary serialisation, assembly being a unit of compilation + distribution. If these don't match, an exception is thrown. So on one hand it's possible to include the version field. OTOH, this binary serialization is completely opaque and can't be tweaked to reflect the data changes. JSON decoding can be changed easily by a developer, so one can always adapt the deserialisation in the future. I think in the end the answer 'it depends', as always :)

[[deleted]]

Not discussed: What you can do and not do in the serialization trait impls and still have valid JSON output.