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

add builtins assumptions #2283

Merged
merged 2 commits into from Aug 4, 2020
Merged

Conversation

JLHwung
Copy link
Contributor

@JLHwung JLHwung commented Jun 25, 2020

We have mentioned this assumption before
babel/babel#7043 (comment)
babel/babel#11372 (comment)
babel/babel#11744 (comment)

but never state it clearly.

@netlify
Copy link

netlify bot commented Jun 25, 2020

Deploy preview for babel ready!

Built without sensitive environment variables with commit be90656

https://deploy-preview-2283--babel.netlify.app

@yortus
Copy link

yortus commented Jun 26, 2020

If this is intended to cover issues like babel/babel#11744 and babel/babel#10807, could you please consider adding the assumption that the code will not have any variables in scope with the same name as builtins. There's nothing spec-incompliant about that and builtins are not modified in such cases, so the current wording misses this assumption.

docs/caveats.md Outdated Show resolved Hide resolved
Co-authored-by: Brian Ng <bng412@gmail.com>
@JLHwung JLHwung merged commit 5a17280 into babel:master Aug 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants