-
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
vm: misleading language #10697
Comments
@mscdex what about just "the caller's context"? |
I'd probably be okay with that too. |
Or, even better, taking the previous sentence into account:
It is as simple as possible and it's not misleading like my previous suggestion actually is, too, after some thinking about it. (The word "caller" sounds like "the caller of require" which is certainly not the case since it may be called from another sandbox). |
Yep :-) (although s/state with context/state with the context/ and s/the this context/the context/) |
Yeah, that's even better. I'll open a PR in a moment. |
@mscdex and "the this" is a typo, I meant just "this" :) |
The note following the http.Server example in the vm documentation contains misleading language. This commit removes the incorrect reference to threads. Fixes: nodejs#10697
The note following the http.Server example in the vm documentation contains misleading language. This commit removes the incorrect reference to threads. Fixes: nodejs#10697 PR-URL: nodejs#10708 Reviewed-By: Brian White <[email protected]> Reviewed-By: James M Snell <[email protected]>
The note following the http.Server example in the vm documentation contains misleading language. This commit removes the incorrect reference to threads. Fixes: nodejs#10697 PR-URL: nodejs#10708 Reviewed-By: Brian White <[email protected]> Reviewed-By: James M Snell <[email protected]>
The note following the http.Server example in the vm documentation contains misleading language. This commit removes the incorrect reference to threads. Fixes: nodejs#10697 PR-URL: nodejs#10708 Reviewed-By: Brian White <[email protected]> Reviewed-By: James M Snell <[email protected]>
The note following the http.Server example in the vm documentation contains misleading language. This commit removes the incorrect reference to threads. Fixes: nodejs#10697 PR-URL: nodejs#10708 Reviewed-By: Brian White <[email protected]> Reviewed-By: James M Snell <[email protected]>
The note following the http.Server example in the vm documentation contains misleading language. This commit removes the incorrect reference to threads. Fixes: #10697 PR-URL: #10708 Reviewed-By: Brian White <[email protected]> Reviewed-By: James M Snell <[email protected]>
The note following the http.Server example in the vm documentation contains misleading language. This commit removes the incorrect reference to threads. Fixes: #10697 PR-URL: #10708 Reviewed-By: Brian White <[email protected]> Reviewed-By: James M Snell <[email protected]>
The note following the
http.Server
example in thevm
documentation contains misleading language. Specifically, it mentions "the calling thread's context" when it has nothing to do with threading since code execution viavm
happens on the same thread. The note makes it sound as if this is not the case.I'm not sure what wording would describe this more accurately. "the parent context?" "the original context?"
The text was updated successfully, but these errors were encountered: