nlupugla

Thanks for the interest! I'll see if I can attach the demo as a zip to the feature PR. It probably isn't working because you need to clone my saveload_api...

Great! I attached a zip to my feature PR too as per your suggestion.

Hi @dalexeev, thanks so much for taking the time to review my demo and provide helpful comments! I'll respond to each of your points. Feel free to reply to me...

Thanks for the feedback :) I think overall you both have convinced me it makes more sense to build on the previous demo rather than use this one, but I...

> In university I remember reading a book where the author takes [Hunt the Wumpus](https://en.wikipedia.org/wiki/Hunt_the_Wumpus) and rewrites it to use proper architecture layers, separations of concerns, etc. Then at the...

Hi folks! Thanks again for your feedback on my demo. I've paused working on this in favor of working on a high-level saving API inspired by the high-level multiplayer API....

Based on my understanding, it looks like users will be able to add and remove fields from their struct at runtime. Is that a "feature" or a "bug" of this...

> @nlupugla No, I think they should not be able to add and remove fields from structs. If you want this kind of flexibility, Dictionary should be used. That would...

> @nlupugla Adding and removing elements would break the ability of the typed optimizer to deal with it, because it will assume a property will always be at the array...

> How would memory be managed for structs? Would they be reference counted, passed by value, manual, or other? They are basically fancy arrays, so I think the memory will...