Dmitriy Khmaladze

Great idea, lets think, I am afraid that only paired operators can be overloaded, need to look at it.

btw, please log issues here: https://github.com/azist/azos the project has moved to the new one

in the next version, not current. [OptionalField] introduces way too much overhead and Slim is not purposed for version tolerance period. You can try using NFX Arow serializer which is...

> Any idea if I could get around it by extending ISerializable and manipulating get/set object data somehow? Absolutely! You can do just what you have described, which is basically...

need to see your code... no idea per description provided

Well, it seems that the stream gets corrupted. That is why they say bin serializers are brittle in general. Are you able to d-serialize the NEXT object in stream after...

> I noticed one thing; If I serialize my object without custom serialization (ISerializable commented out) I **cannot deserialize it with ISerializable back on**, and vice versa. It is always...

> So suppose I have an instance of MyClass stored, which I serialized with slim (without ISerializable). And now I want to add a new field Slim serializer purposely was...

Yes, this happened 12/19, then today, it happens very infrequently a'la heisenbug - which makes me think that this is multi-threading related issue (improper locking/barrier/sequencing/race)

The ``_entry`` gobbles up ram like crazy, we have to be mindful with additional field creation as it makes these ``_entry[]`` bigger and bigger But at least we have **figured...