-
Notifications
You must be signed in to change notification settings - Fork 30k
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
src: clean up program/isolate/env init logic #9224
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with green CI
I started the CI yesterday but it doesn't show up. New run: https://ci.nodejs.org/job/node-test-pull-request/4618/ |
Some red there but they appear to be unrelated. |
NodeInstanceData is not used meaningfully and makes the initialization logic harder to follow. Let's remove it and delete 100 lines of code in one fell swoop. PR-URL: nodejs#9224 Reviewed-By: James M Snell <jasnell@gmail.com>
Reorder the initialization logic so that program-wide, per-isolate and per-environment initialization is more cleanly separated. PR-URL: nodejs#9224 Reviewed-By: James M Snell <jasnell@gmail.com>
a98e719
to
ceb6023
Compare
NodeInstanceData is not used meaningfully and makes the initialization logic harder to follow. Let's remove it and delete 100 lines of code in one fell swoop. PR-URL: #9224 Reviewed-By: James M Snell <jasnell@gmail.com>
Reorder the initialization logic so that program-wide, per-isolate and per-environment initialization is more cleanly separated. PR-URL: #9224 Reviewed-By: James M Snell <jasnell@gmail.com>
@bnoordhuis should this be backported? I'm assuming it shouldn't land on v4. It does not land cleanly on v6. Please feel free to update labels |
Back-porting isn't necessary unless it causes conflicts for other pull requests. Let me know if that is the case. |
General cleanup: