You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To be able to switch underlying serialization format flexibly (and not just struct version number which is possible right now), idea was to reserve ubyte.max version number to mean "extended header follows" and using additional decorator layer which pick serializer object depending on data in that header.
The text was updated successfully, but these errors were encountered:
AKA serializer/loader with metadata.
To be able to switch underlying serialization format flexibly (and not just struct version number which is possible right now), idea was to reserve
ubyte.max
version number to mean "extended header follows" and using additional decorator layer which pick serializer object depending on data in that header.The text was updated successfully, but these errors were encountered: