-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jsrt: JsCreateExternalObjectWithPrototype #4267
jsrt: JsCreateExternalObjectWithPrototype #4267
Conversation
Also sent nodejs/node-chakracore#429 to node-chakracore using this new API. |
@@ -122,4 +122,12 @@ | |||
JsHasOwnProperty | |||
JsCopyStringOneByte | |||
JsGetDataViewInfo | |||
JsCreateExternalObjectWithPrototype | |||
JsObjectGetProperty |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Were these missing accidentally prior to now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: don't the native tests generally use the Catch unittest framework for us?
current design of the xplat native tests doesn't require |
Merge pull request #4267 from obastemur:Jsrt_external_with_proto node-chakracore, each `ObjectTemplate` creation first creates an external object and sets prototype separately. `JsSetPrototype` is decently expensive to lazy call. This new `JsCreateExternalObjectWithPrototype` should supersede `JsCreateExternalObject` since prototype can be provided as `nullptr` if there is none. Also VS export Jsrt***ObjectProperty
node-chakracore, each
ObjectTemplate
creation first creates an external object and sets prototype separately.JsSetPrototype
is decently expensive to lazy call.This new
JsCreateExternalObjectWithPrototype
should supersedeJsCreateExternalObject
since prototype can be provided asnullptr
if there is none.Also VS export Jsrt***ObjectProperty