Skip to content
This repository was archived by the owner on Mar 29, 2024. It is now read-only.

Conversation

@PeeHaa
Copy link
Contributor

@PeeHaa PeeHaa commented Sep 5, 2016

No description provided.

@pinepain
Copy link
Member

pinepain commented Sep 5, 2016

Wow! @PeeHaa! Thanks for your contribution, I really appreciate it.

P.S. you are far more advanced than me, so it probably a reminder to further contributors that you may add [skip ci] to commit message to prevent triggering CI when editing project files that doesn't affects functionality, like readme, stubs, some examples.

- hides complexity with isolates and contexts scope management under the hood;
- no magic; no assumptions;
- does what it is asked to do;
- hides complexity by isolation and contexts scope management under the hood;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are v8::Isolate and v8::Context concepts in v8 engine. Isolate could be accessed by only one thread at a time and multiple Contexts could reside in it at the same time. To perform some operations in v8 in C++ you need to enter Isolate, enter Context, do you job and then leave it (it's not pretty accurate explanation, but for simplicity let it be this way at this time).

So I tried to say that this entering/leaving is hidden under the hood and done automatically when needed transparently to the user.

@pinepain pinepain closed this in aa9fb6e Sep 8, 2016
@pinepain
Copy link
Member

pinepain commented Sep 8, 2016

Thanks @PeeHaa!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants