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

Use undefined, not null, as the default this value when invoking callbacks, to align with the ES6 specification. #6

Closed
wants to merge 1 commit into from
Closed

Use undefined, not null, as the default this value when invoking callbacks, to align with the ES6 specification. #6

wants to merge 1 commit into from

Conversation

bzbarsky
Copy link
Collaborator

@bzbarsky bzbarsky commented Jan 9, 2014

@marcoscaceres
Copy link
Member

Just wondering, is there a need to make a distinction here between the strict and non-strict modes? The original bug mentions strict mode as specifically requiring this behavior, but I was not sure about non-strict mode.

@bzbarsky
Copy link
Collaborator Author

bzbarsky commented Jan 9, 2014

There is not. The strict vs non-strict distinction is handled by the [[Call]] of non-strict functions.

@bzbarsky bzbarsky closed this Jan 10, 2014
@noamr noamr mentioned this pull request Jul 15, 2024
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@bzbarsky @marcoscaceres @heycam