Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Normative: Make eval?.() direct eval. #2063

Closed
wants to merge 1 commit into from
Closed

Normative: Make eval?.() direct eval. #2063

wants to merge 1 commit into from

Conversation

rkirsling
Copy link
Member

Resolves #2062.

@ljharb ljharb added needs consensus This needs committee consensus before it can be eligible to be merged. needs test262 tests The proposal should specify how to test an implementation. Ideally via github.com/tc39/test262 normative change Affects behavior required to correctly evaluate some ECMAScript source text labels Jun 24, 2020
@rkirsling
Copy link
Member Author

Closing; we decided to leave the spec as-is in today's meeting.

@rkirsling rkirsling closed this Jul 20, 2020
@rkirsling rkirsling deleted the direct-optional-eval branch July 20, 2020 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@michaelficarra michaelficarra michaelficarra approved these changes

Assignees
No one assigned
Labels
needs consensus This needs committee consensus before it can be eligible to be merged. needs test262 tests The proposal should specify how to test an implementation. Ideally via github.com/tc39/test262 normative change Affects behavior required to correctly evaluate some ECMAScript source text
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Should eval?.() be direct eval?
3 participants
@rkirsling @michaelficarra @ljharb