Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Serde support for World #40
This PR implements support for serde 1.0. Users implement
An example that roundtrips data by serializing, deserializing and then serializing again is provided, whereby the entity-UUID mappings are maintained through the whole process.
Please tell me all the ways in which this is unsound.
I'll squash commits before merge.
We could include the type UUID mappings too, perhaps under a feature flag. The main reason is that users may want to use something other than UUIDs for persistent type identifiers, so I think the current trait API should still be exposed, but we can also include the type UUID implementation as an easy-to-use default?
Sorry for letting this sit for so long. Serialisation as a whole will still need some more work (such as including more of a default setup in-box) before release, but what is implemented here looks good and is behind a non-default feature flag for now anyway.
Other serialisation cases, such as what someone might need for networking, will need further discussion elsewhere as it will likely be quite different to what is implemented in this PR.