-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
lib: remove unnecessary lazy loading in internal/encoding
#45810
lib: remove unnecessary lazy loading in internal/encoding
#45810
Conversation
Is the lazy loading valid in |
Folks using a build of Node.js without the snapshot are choosing a slower bootstrap to get a better smaller binary, and since this change doesn't impact the binary size, I expect they don't really care about it. |
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.
Without such a function, I guess that a module now snapshotted would be hard to detect when it won't need to be snapshotted in the future. However, I agree with this change since it seems hard to make buffer
not snapshotted even in the future.
Landed in aa2ca81 |
PR-URL: #45810 Reviewed-By: Daeyeon Jeong <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
PR-URL: #45810 Reviewed-By: Daeyeon Jeong <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
PR-URL: #45810 Reviewed-By: Daeyeon Jeong <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
PR-URL: #45810 Reviewed-By: Daeyeon Jeong <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
PR-URL: #45810 Reviewed-By: Daeyeon Jeong <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
PR-URL: #45810 Reviewed-By: Daeyeon Jeong <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
Requesting a backport to v18.x since it broke some tests in v18.x-staging. |
node:buffer
is snapshotted, so there's no benefit in lazy loading it.