Refactor child mapping & scope boundary detection #348
Conversation
This file contains 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
This is a refactor with no intended semantic changes. It addresses some "TODO" comments in the source by creating a generic fmap-like facility for mapping over child nodes. I also factored out scope boundary detection. In addition to helping readability, this makes it easier to safely introduce future constructs (like ES6 arrow function expressions) that are also scope boundaries.
|
❤️ |
michaelficarra
added a commit
that referenced
this pull request
May 28, 2015
Refactor child mapping & scope boundary detection
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a refactor with no intended semantic changes. It addresses some "TODO" comments in the source by creating a generic fmap-like facility for mapping over child nodes.
I also factored out scope boundary detection. In addition to helping readability, this makes it easier to safely introduce future constructs (like ES6 arrow function expressions) that are also scope boundaries.