Implement serializeSelf/deserializeSelf for Map, Set, and WeakMap #1980
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.
This PR allows for serialization of native Map, Set, and WeakMap. Instead of pointing the serialization
prototype
to a moduleId, it points to the constructor directly e.g."prototype": "Map"
Set
Set#deserializeSelf()
looks for avalues
property.Set#serializeSelf()
generates this structureMap & Weak Map
Map#deserializeSelf()
andWeakMap#deserializeSelf()
support the same serialization structures. Each can be serialized in two ways.keys
andvalues
arrays wherekeys[i] ==> values[i]
This structure is more efficient to deserialize than the second so
Map#serializeSelf()
andWeakMap#serializeSelf()
both produce this version.entries
array where each item in the array is an object with a key and value property