-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Editorial: Fix indirect eval environment check #1949
Editorial: Fix indirect eval environment check #1949
Conversation
I would call this an editorial bugfix, since an assertion is violated in the current text. |
72088e6
to
a7962fe
Compare
I agree with editorial here -- this is a spec bug. There's no consensus needed here, and certainly no tests needed. There is no other interpretation of indirect eval possible in the current spec or in any implementation. |
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 @bakkot's suggestion
a7962fe
to
9352535
Compare
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 otherwise.
9352535
to
cbe3b05
Compare
indirect eval should not allow
new.target
,super
, etc., andGetThisEnvironment
is not defined in terms of non-ecmascript execution contexts.