-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
fs: use kMaxLength
from binding
#1903
Conversation
@@ -19,7 +19,7 @@ const Readable = Stream.Readable; | |||
const Writable = Stream.Writable; | |||
|
|||
const kMinPoolSpace = 128; | |||
const kMaxLength = require('internal/smalloc').kMaxLength; | |||
const kMaxLength = process.binding('smalloc').kMaxLength; |
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.
Femto-nit: you have one space too many after the '='.
LGTM with style nit. Can you update the commit log to explicitly call out graceful-fs and add a link to the issue you filed there? I don't want people to construe this change as an implicit promise of support for eval-ing core modules. |
717ad44
to
443a72c
Compare
@bnoordhuis PTAL at the message |
LGTM but can you use |
Sorry, I mean: EDIT: The commit history is a bit inconsistent in its use of Refs vs. See. |
This allows `graceful-fs` to evaluate `fs` source without access to internals. This is a temporary workaround that makes npm work. See: isaacs/node-graceful-fs#41 Fixes: nodejs#1898
443a72c
to
4fd4838
Compare
This allows `graceful-fs` to evaluate `fs` source without access to internals. This is a temporary workaround that makes npm work. See: isaacs/node-graceful-fs#41 Fixes: #1898 PR-URL: #1903 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Landed in 2dcef83 |
This allows userland modules to evaluate
fs
sourcewithout access to internals.
Fixes: #1898
R=@evanlucas