Add Serializable
and Transferable
interfaces
#1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
Serializable
interface has two methods defined by the well-known symbolsSymbol.for('bare.serialize')
andSymbol.for('bare.deserialize')
. The former is an instance method that returns a serializable representation of the class instance. The latter is a class method that takes that same representation and creates a class instance.Likewise, the
Transferable
interface two methods defined by the well-known symbolsSymbol.for('bare.detach')
andSymbol.for('bare.attach')
as well as an optional nameddetached
property. The former method is an instance method that detaches the class instance and returns a serializable representation of the data to transfer, such as anExternal
pointer. The former method is a class method that takes that same data and creates a class instance with the data attached.To actually use classes that implement these interfaces during serialization and deserialization, the classes must be registered. This happens via new function arguments:
Attempts to serialize or transfer unregistered interfaces will throw.