Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
feat(ses): Support global lexicals #356
feat(ses): Support global lexicals #356
Changes from 1 commit
0bfee80
52c9813
0c0d41c
b00e8ab
dd3e733
b6f8cb0
599a865
8ae2f58
dc195a6
360fe9a
a954c4d
48f98a1
29386e2
32269f2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
yeah, do we not need this protection in this one case because we created
globalLexicals
ourselves, and know that it doesn't contain any accessors? I'm happy to retain thereflectGet
for safety, but we might amend the comment if we know that's why we're doing it, and point out the difference betweenglobalLexicals
(which we create, and is static) andendowments
(which.. might come from the user, and might have accessors, which we're happy to let execute, but not let those accessors use ourthis
object?)