-
Notifications
You must be signed in to change notification settings - Fork 510
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
Support Isolate::RunMicrotasks #914
Comments
@romgrk What exactly are you looking for here? The change you linked is not an API change. |
Wdym by not an API change? It was previously #if V8_MAJOR_VERSION >= 9
Isolate::GetCurrent()->PerformMicrotaskCheckpoint();
#else
Isolate::GetCurrent()->RunMicrotasks();
#endif |
@romgrk Could it be that you’re thinking about a different V8 commit then? Only changes to That being said – Node.js addons should generally not run the microtask queue manually, because Node.js itself manages it. Do you have a specific use case in mind? |
Ok, not that's the commit I'm thinking about, not sure how you classify what goes in or not but I was under the impression that this was for anything that needs to be specialized for different V8 versions.
I know, but my addon isn't like most of them :| I need to stop nodejs event loop to replace it with GTK's event loop and call But anyway, this is quite small and I understand it's a very rare use-case, I can live with doing the check in my codebase, you can close if you don't plan to include it. |
Was merged with MicrotaskQueue::RunMicrotasks:
v8/v8@ba363c7
The text was updated successfully, but these errors were encountered: