Summary:

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains two APIs to copy objects from one runtime to another runtime.

Two methods are introduced in this interface:

`serialize` will take in some JS value (represented by `jsi::Value`) and
serialize the object into an opaque `Serialize` object. The lifetime of
the serialized object is independent from the original object.

`deserialize` will take in the serialized object and deserialize it into
the runtime, returning the created JS object.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu

Differential Revision: D76547681

Summary:

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains two APIs to copy objects from one runtime to another runtime.

Two methods are introduced in this interface:

`serialize` will take in some JS value (represented by `jsi::Value`) and
serialize the object into an opaque `Serialize` object. The lifetime of
the serialized object is independent from the original object.

`deserialize` will take in the serialized object and deserialize it into
the runtime, returning the created JS object.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu

Differential Revision: D76547681

Summary:
Pull Request resolved: facebook#52624

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains two APIs to copy objects from one runtime to another runtime.

Two methods are introduced in this interface:

`serialize` will take in some JS value (represented by `jsi::Value`) and
serialize the object into an opaque `Serialize` object. The lifetime of
the serialized object is independent from the original object.

`deserialize` will take in the serialized object and deserialize it into
the runtime, returning the created JS object.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu

Differential Revision: D76547681

Summary:

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains two APIs to copy objects from one runtime to another runtime.

Two methods are introduced in this interface:

`serialize` will take in some JS value (represented by `jsi::Value`) and
serialize the object into an opaque `Serialize` object. The lifetime of
the serialized object is independent from the original object.

`deserialize` will take in the serialized object and deserialize it into
the runtime, returning the created JS object.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu

Differential Revision: D76547681

Summary:
Pull Request resolved: facebook#52624

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains two APIs to copy objects from one runtime to another runtime.

Two methods are introduced in this interface:

`serialize` will take in some JS value (represented by `jsi::Value`) and
serialize the object into an opaque `Serialize` object. The lifetime of
the serialized object is independent from the original object.

`deserialize` will take in the serialized object and deserialize it into
the runtime, returning the created JS object.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu

Differential Revision: D76547681

Summary:

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains two APIs to copy objects from one runtime to another runtime.

Two methods are introduced in this interface:

`serialize` will take in some JS value (represented by `jsi::Value`) and
serialize the object into an opaque `Serialize` object. The lifetime of
the serialized object is independent from the original object.

`deserialize` will take in the serialized object and deserialize it into
the runtime, returning the created JS object.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu

Differential Revision: D76547681

Summary:
Pull Request resolved: facebook#52624

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains two APIs to copy objects from one runtime to another runtime.

Two methods are introduced in this interface:

`serialize` will take in some JS value (represented by `jsi::Value`) and
serialize the object into an opaque `Serialize` object. The lifetime of
the serialized object is independent from the original object.

`deserialize` will take in the serialized object and deserialize it into
the runtime, returning the created JS object.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu

Differential Revision: D76547681

Summary:

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains two APIs to copy objects from one runtime to another runtime.

Two methods are introduced in this interface:

`serialize` will take in some JS value (represented by `jsi::Value`) and
serialize the object into an opaque `Serialize` object. The lifetime of
the serialized object is independent from the original object.

`deserialize` will take in the serialized object and deserialize it into
the runtime, returning the created JS object.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu

Differential Revision: D76547681

Summary:
Pull Request resolved: facebook#52624

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains two APIs to copy objects from one runtime to another runtime.

Two methods are introduced in this interface:

`serialize` will take in some JS value (represented by `jsi::Value`) and
serialize the object into an opaque `Serialize` object. The lifetime of
the serialized object is independent from the original object.

`deserialize` will take in the serialized object and deserialize it into
the runtime, returning the created JS object.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu

Differential Revision: D76547681

Summary:

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains two APIs to copy objects from one runtime to another runtime.

Two methods are introduced in this interface:

`serialize` will take in some JS value (represented by `jsi::Value`) and
serialize the object into an opaque `Serialize` object. The lifetime of
the serialized object is independent from the original object.

`deserialize` will take in the serialized object and deserialize it into
the runtime, returning the created JS object.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu

Differential Revision: D76547681

Summary:

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains two APIs to copy objects from one runtime to another runtime.

Two methods are introduced in this interface:

`serialize` will take in some JS value (represented by `jsi::Value`) and
serialize the object into an opaque `Serialize` object. The lifetime of
the serialized object is independent from the original object.

`deserialize` will take in the serialized object and deserialize it into
the runtime, returning the created JS object.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu

Differential Revision: D76547681

Summary:

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains two APIs to copy objects from one runtime to another runtime.

Two methods are introduced in this interface:

`serialize` will take in some JS value (represented by `jsi::Value`) and
serialize the object into an opaque `Serialize` object. The lifetime of
the serialized object is independent from the original object.

`deserialize` will take in the serialized object and deserialize it into
the runtime, returning the created JS object.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu

Differential Revision: D76547681

Summary:

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains two APIs to copy objects from one runtime to another runtime.

Two methods are introduced in this interface:

`serialize` will take in some JS value (represented by `jsi::Value`) and
serialize the object into an opaque `Serialize` object. The lifetime of
the serialized object is independent from the original object.

`deserialize` will take in the serialized object and deserialize it into
the runtime, returning the created JS object.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu

Differential Revision: D76547681

Summary:

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains two APIs to copy objects from one runtime to another runtime.

Two methods are introduced in this interface:

`serialize` will take in some JS value (represented by `jsi::Value`) and
serialize the object into an opaque `Serialize` object. The lifetime of
the serialized object is independent from the original object.

`deserialize` will take in the serialized object and deserialize it into
the runtime, returning the created JS object.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu

Differential Revision: D76547681

Summary:

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains two APIs to copy objects from one runtime to another runtime.

Two methods are introduced in this interface:

`serialize` will take in some JS value (represented by `jsi::Value`) and
serialize the object into an opaque `Serialize` object. The lifetime of
the serialized object is independent from the original object.

`deserialize` will take in the serialized object and deserialize it into
the runtime, returning the created JS object.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu

Differential Revision: D76547681

Summary:

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains two APIs to copy objects from one runtime to another runtime.

Two methods are introduced in this interface:

`serialize` will take in some JS value (represented by `jsi::Value`) and
serialize the object into an opaque `Serialize` object. The lifetime of
the serialized object is independent from the original object.

`deserialize` will take in the serialized object and deserialize it into
the runtime, returning the created JS object.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu, fbmal7

Differential Revision: D76547681

Summary:

Changelog: [Internal]

Add a new optional interface `ISerialization` to JSI. This interface
contains four APIs to clone objects from one runtime to another runtime.

Four methods are introduced in this interface:
* `serialize`: Takes in a JS value (represented by `jsi::Value`) and
serialize the value into an opaque `Serialized` object.

* `deserialize`: Takes in the `Serialized` object created by `serialize`
and deserialize it into the runtime, returning the created JS value.

* `serializeWithTransfer`: Takes in a JS value (represented by
`jsi::Value`) and a `transferList` (a `jsi::Array` of `jsi::Value`s).
This will serialize the `value` into an opaque `Serialize` object and
transfer the ownership of everything in `transferList` into the
`Serialized` object. If any non-transferable values is passed into the
transferList, this will throw. This `Serialized` object must only be
deserialized once.

* `deserializeWithTransfer`: Takes in the `Serialized` object created by
`serializeWithTransfer`. It will deserialize the object into the runtime
and  any value owned by the `Serialized` object will now be owned by the
current runtime. It will return an `jsi::Array` where the first value is
the deserialized value passed into `serializeWithTransfer`, followed by
all transferred values.

The lifetime of the `Serialized` object created from the APIs is
independent of the original object and runtime.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Reviewed By: dannysu, fbmal7

Differential Revision: D76547681

Summary:
X-link: facebook/react-native#52624

Add a new optional interface `ISerialization` to JSI. This interface
contains four APIs to clone objects from one runtime to another runtime.

Four methods are introduced in this interface:
* `serialize`: Takes in a JS value (represented by `jsi::Value`) and
serialize the value into an opaque `Serialized` object.

* `deserialize`: Takes in the `Serialized` object created by `serialize`
and deserialize it into the runtime, returning the created JS value.

* `serializeWithTransfer`: Takes in a JS value (represented by
`jsi::Value`) and a `transferList` (a `jsi::Array` of `jsi::Value`s).
This will serialize the `value` into an opaque `Serialize` object and
transfer the ownership of everything in `transferList` into the
`Serialized` object. If any non-transferable values is passed into the
transferList, this will throw. This `Serialized` object must only be
deserialized once.

* `deserializeWithTransfer`: Takes in the `Serialized` object created by
`serializeWithTransfer`. It will deserialize the object into the runtime
and  any value owned by the `Serialized` object will now be owned by the
current runtime. It will return an `jsi::Array` where the first value is
the deserialized value passed into `serializeWithTransfer`, followed by
all transferred values.

The lifetime of the `Serialized` object created from the APIs is
independent of the original object and runtime.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Changelog: [Internal]

Reviewed By: dannysu, fbmal7

Differential Revision: D76547681

fbshipit-source-id: 0c774f3f469c26d3894cac179f4ce5e32cf5ad7f

Summary:
X-link: facebook/react-native#52624

Add a new optional interface `ISerialization` to JSI. This interface
contains four APIs to clone objects from one runtime to another runtime.

Four methods are introduced in this interface:
* `serialize`: Takes in a JS value (represented by `jsi::Value`) and
serialize the value into an opaque `Serialized` object.

* `deserialize`: Takes in the `Serialized` object created by `serialize`
and deserialize it into the runtime, returning the created JS value.

* `serializeWithTransfer`: Takes in a JS value (represented by
`jsi::Value`) and a `transferList` (a `jsi::Array` of `jsi::Value`s).
This will serialize the `value` into an opaque `Serialize` object and
transfer the ownership of everything in `transferList` into the
`Serialized` object. If any non-transferable values is passed into the
transferList, this will throw. This `Serialized` object must only be
deserialized once.

* `deserializeWithTransfer`: Takes in the `Serialized` object created by
`serializeWithTransfer`. It will deserialize the object into the runtime
and  any value owned by the `Serialized` object will now be owned by the
current runtime. It will return an `jsi::Array` where the first value is
the deserialized value passed into `serializeWithTransfer`, followed by
all transferred values.

The lifetime of the `Serialized` object created from the APIs is
independent of the original object and runtime.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Changelog: [Internal]

Reviewed By: dannysu, fbmal7

Differential Revision: D76547681

fbshipit-source-id: 0c774f3f469c26d3894cac179f4ce5e32cf5ad7f

Summary:
X-link: facebook/react-native#52624

Add a new optional interface `ISerialization` to JSI. This interface
contains four APIs to clone objects from one runtime to another runtime.

Four methods are introduced in this interface:
* `serialize`: Takes in a JS value (represented by `jsi::Value`) and
serialize the value into an opaque `Serialized` object.

* `deserialize`: Takes in the `Serialized` object created by `serialize`
and deserialize it into the runtime, returning the created JS value.

* `serializeWithTransfer`: Takes in a JS value (represented by
`jsi::Value`) and a `transferList` (a `jsi::Array` of `jsi::Value`s).
This will serialize the `value` into an opaque `Serialize` object and
transfer the ownership of everything in `transferList` into the
`Serialized` object. If any non-transferable values is passed into the
transferList, this will throw. This `Serialized` object must only be
deserialized once.

* `deserializeWithTransfer`: Takes in the `Serialized` object created by
`serializeWithTransfer`. It will deserialize the object into the runtime
and  any value owned by the `Serialized` object will now be owned by the
current runtime. It will return an `jsi::Array` where the first value is
the deserialized value passed into `serializeWithTransfer`, followed by
all transferred values.

The lifetime of the `Serialized` object created from the APIs is
independent of the original object and runtime.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Changelog: [Internal]

Reviewed By: dannysu, fbmal7

Differential Revision: D76547681

fbshipit-source-id: 0c774f3f469c26d3894cac179f4ce5e32cf5ad7f

Summary:
X-link: facebook/react-native#52624

Add a new optional interface `ISerialization` to JSI. This interface
contains four APIs to clone objects from one runtime to another runtime.

Four methods are introduced in this interface:
* `serialize`: Takes in a JS value (represented by `jsi::Value`) and
serialize the value into an opaque `Serialized` object.

* `deserialize`: Takes in the `Serialized` object created by `serialize`
and deserialize it into the runtime, returning the created JS value.

* `serializeWithTransfer`: Takes in a JS value (represented by
`jsi::Value`) and a `transferList` (a `jsi::Array` of `jsi::Value`s).
This will serialize the `value` into an opaque `Serialize` object and
transfer the ownership of everything in `transferList` into the
`Serialized` object. If any non-transferable values is passed into the
transferList, this will throw. This `Serialized` object must only be
deserialized once.

* `deserializeWithTransfer`: Takes in the `Serialized` object created by
`serializeWithTransfer`. It will deserialize the object into the runtime
and  any value owned by the `Serialized` object will now be owned by the
current runtime. It will return an `jsi::Array` where the first value is
the deserialized value passed into `serializeWithTransfer`, followed by
all transferred values.

The lifetime of the `Serialized` object created from the APIs is
independent of the original object and runtime.

Note that objects can only be copied into another runtime instance of
the same type. For example, a serialized object produced by the Hermes
runtime can only be deserialized by another Hermes runtime.

Changelog: [Internal]

Reviewed By: dannysu, fbmal7

Differential Revision: D76547681

fbshipit-source-id: 0c774f3f469c26d3894cac179f4ce5e32cf5ad7f