Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Refactoring how internal C objects are stored in V8 and passed to JS #240

Copy link
Copy link
@johnhaley81

Description

@johnhaley81
Issue body actions

This change is from the awesome example that was in #239.

So basically, each V8 wrapper object will need to store all of the objects that it's C object has in it's own private wrapper object. Any getters/setters for these objects will have to unwrap these private variables to access the internal data.

We can't just create wrapper classes on the fly when the user requests data since when those wrapper classes are destroyed they also destroy the data that they wrapped.

I'm assigning @maxkorp to take care of this. If you have any questions feel free to ask.

Reactions are currently unavailable

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.