Fix #14620: Lookup names in exports as well as locals when binding special properties#14823
Conversation
…ecial properties
Contributor
|
question. why we still look things in "locals" should all export stuffs be in "exports" ? (I guess I don't understand this
|
Contributor
Author
|
it might not be exported.. e.g.: // global script
class C {}
C.static = 0 |
sandersn
approved these changes
Apr 14, 2017
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We only looked up names for special property targets in
container.local, that got us the local symbol if they were exported. The change looks in theexportsof the container first, if one exists.