However, the expectation is that these subclasses would have the same constructur signature as their native base class. When copying, we explicitly reuse the constructor of the original object. Starting in ES2015, native globals can be subclassed like any custom class. The constructor of the original object is used, instead of using known globals As such, the original reference is copied. While it would be relatively trivial to copy over the message and stack to a new object of the same Error subclass, it is a common practice to "override" the message or stack, and copies would not retain this mutation.
Error references are copied directly, instead of creating a new *Error object If your use-cases require different handling, you can always create your own custom copier with createCopier or createStrictCopier. For this library, some decisions were explicitly made for the default copiers of specific object types, and those decisions are detailed below. Inherently, what is considered a valid copy is subjective because of different requirements and use-cases. The benchmarks quoted below are based on use of WeakSet. By default, a cache based on WeakSet is used, but if WeakSet is not available then a fallback is used. The following object types are copied directly, as they are either primitives, cannot be cloned, or the common use-case implementation does not expect cloning:Ĭircular objects are supported out of the box.
import copy from 'fast-copy' Ĭonst copied = copy(), Generator objects are copied, but still reference the original generator's stateĬonsole.log(copiedObject = object) // falseĬonsole.log(deepEqual(copiedObject, object)) // true API copyĭeeply copy the object passed.The constructor of the original object is used, instead of using known globals.Error references are copied directly, instead of creating a new *Error object.A blazing fast deep object copier Table of contents
0 kommentar(er)
