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.

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

Avoid lazy parsing the function body of AMP extensions. #3979

Merged
merged 1 commit into from
Jul 8, 2016

Conversation

cramforce
Copy link
Member

Fixes #3977

@erwinmombay
Copy link
Member

@cramforce interesting, so no need for the IIFE and just needs the parens huh?

@erwinmombay
Copy link
Member

@cramforce have you tried timing the eval time on it?

@cramforce
Copy link
Member Author

IIFE cannot be needed. Otherwise they'd need to parse to the end to determine whether they should have parsed :)

This basically cannot be benchmarked. The only place this can be seen is in Chrome traces.

@cramforce cramforce merged commit af63a88 into ampproject:master Jul 8, 2016
@cramforce cramforce deleted the non-lazy-parsing branch July 11, 2016 18:34
ariangibson pushed a commit to Mixpo/amphtml that referenced this pull request Sep 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants