Every time I implement a new thing in MidBoss the amount of time I have to spend on it is about 1 part actually implementing it and 2 parts saving+loading logichttps://twitter.com/jcd748/status/1190848791672446977 …
-
-
I feel compelled to point out that the circular references thing was an example of how serialization is more complex than it might initially seems that laypeople could easily understand, not something I believe is somehow unsolved or unsolvable
-
Well, I suppose it depends on the perspective, but I'm not sure I see how it affects the complexity of the problem in any way one would ordinarily notice. It is literally just "Slot = Serialize(X);" becomes "if(!Table[X]) {Table[X] = Serialize(X);} Slot = Table[X];" Right?
- Show replies
New conversation -
-
-
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.
-
Yes, and also dual interpretations it didn't handle (two pointers to the same thing that claimed to be different types). Both of these would be pretty easy to handle if you were trying to make a system that was meant to be a "standard" system people could use as a library.
- Show replies
New conversation -
-
-
I think havok also had generic serialization pretty early.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.