De/serialize De/serializer Traits

[krakow10]

Taking inspiration from serde, rbx-dom could define RbxSerialize, RbxSerializer, RbxDeserialize, RbxDeserializer traits as an interface between rbx_dom_weak and rbx_binary / rbx_xml. These would perhaps include member functions to read/write the different chunk types, or property types, or however the best way to make it is. Idea; try deferred prop chunks.

I can imagine several benefits:

• Runtime Instance Data #514 A custom deserialize implementation can define its own data bag, meaning library consumers don't need to wrap the dom with their own dom to get owned data into their instances
• Ustr Concerns & Footguns #515 A new way to drop ustr, hooray!
• rbx_dom_strong #92 Extendable to rbx_dom_strong

Do you think this idea has any substance? The main advantage would be reusing deserialization code and sharing Dom code with rbx_dom_strong, perhaps even having a single generic Dom<Instance> type with StrongInstance and WeakInstance. I thought I'd share my thoughts before exploring this.