It is also worth noting that Granny 2.x shipped out of the box with a generic C serializer that handled circular references, discriminated unions, endianness conversion, and version remapping for arbitrary data structures. And that was in 2002.
Also now I am kind of off on a tangent of thinking about what the most efficient way is to make a system that handles interior pointers properly :) I feel like it requires two traversals. But I would love to be wrong about that.
-
-
If you always hit the outer container first, it seems do-able. I wonder if you can enforce that in some way by choosing breadth versus depth at certain points.
-
But there's no way to ensure that, right - you could have your top-level container point to two things, one of which is inside the other, and you have no idea which order to do them in. Even if you go in local size order, you can't guarantee something bigger isn't coming later.
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.