At the moment the only preserve process to deal with classes is to go through and save their attributes, then hand them back later with one of the RestoreMethods. This doesn't allow support for a class that might have a temporary or reconstructable attribute that isn't preservable. Adding a way for a class to register its own method used when preserving it would allow this.
At the moment the only preserve process to deal with classes is to go through and save their attributes, then hand them back later with one of the `RestoreMethods`. This doesn't allow support for a class that might have a temporary or reconstructable attribute that isn't `preservable`. Adding a way for a class to register its own method used when preserving it would allow this.
At the moment the only preserve process to deal with classes is to go through and save their attributes, then hand them back later with one of the
RestoreMethods. This doesn't allow support for a class that might have a temporary or reconstructable attribute that isn'tpreservable. Adding a way for a class to register its own method used when preserving it would allow this.Plan is to implement this with the new PreservableType structure - recording preserve and restore methods independently for each class/type.
Support for generic preserve and restore methods added in
a0e8071f5f