The only significant thing it doesn't handle well is references to structures inside other structures, e.g. you have a vec3 and elsewhere you have a pointer to the "y" component. This is something we discussed fixing, but it's a sufficiently rare case.
And I haven't given that problem any thought, but my first reaction is that if you allow people to write arbitrary initialization functions for objects, I don't see any way to really guarantee proper serialization. I mean how can the serialization system analyze that?
-
-
So it seems like a mildly terrifying paradigm to embrace because you move from an easily-solvable problem (C struct graph serialization) to a potentially impossible problem (interdependent function order serialization?) and that sounds like the ultimate sadness.
-
The ultimate sadness is pretty much it. I don't know how other C# devs deal with it, personally I just have a serialize/deserialize method pair now that renders to/from primitive value types. Tends to be a lot more doable, robust, secure, and performant
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.