Skip to content

Conversation

@obastemur
Copy link
Collaborator

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

@obastemur
Copy link
Collaborator Author

Also sent nodejs/node-chakracore#429 to node-chakracore using this new API.

JsCopyStringOneByte
JsGetDataViewInfo
JsCreateExternalObjectWithPrototype
JsObjectGetProperty
Copy link
Contributor

@MSLaguana MSLaguana Nov 17, 2017

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?

Copy link
Contributor

@jackhorton jackhorton left a 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?

@obastemur
Copy link
Collaborator Author

current design of the xplat native tests doesn't require catch framework.

@chakrabot chakrabot merged commit 7bf59d1 into chakra-core:master Nov 20, 2017
chakrabot pushed a commit that referenced this pull request Nov 20, 2017
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants