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

Conversation

backes
Copy link
Member

@backes backes commented Sep 4, 2025

Replace any call to Object::GetIsolate() by Isolate::GetCurrent().
This does not change anything, as Object::GetIsolate() is already implemented as Isolate::GetCurrent() under the hood.

Medium term, some of the new calls could / should be replaced by passing an existing isolate pointer, which can be more efficient depending on usage patterns and the platform that we execute on.

One drive-by fix: Replace linked_requests_data.As<Array>() by linked_requests_data.As<Value>().As<Array>() to fix debug builds.

@backes
Copy link
Member Author

backes commented Sep 4, 2025

@pthier PTAL

Not sure why compilation did not fail when calling these deprecated methods; I fixed everything that failed in #219. This now removes all remaining calls so we can actually remove the deprecated API.

@backes backes changed the title Replace get isolate by isolate getcurrent Replace GetIsolate() by Isolate::GetCurrent() Sep 5, 2025
@pthier
Copy link

pthier commented Sep 5, 2025

Thanks, LGTM

@pthier pthier merged commit 866bc4a into v8:node-ci-2025-08-20 Sep 5, 2025
11 of 17 checks passed
@backes backes deleted the replace-get-isolate-by-isolate-getcurrent branch September 5, 2025 07:44
victorgomes pushed a commit that referenced this pull request Sep 26, 2025
* via gemini: Replace GetIsolate by Isolate::GetCurrent()

* Manual fixes
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.

2 participants

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