More info from lambda lifting + allow global captures #898
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 PR has two changes to lambda lifting.
First, we now return a more precise value describing the changes made during the transformation (e.g., we don't depend on iteration order of
Names in aMap, we store both the names of captured variables and their corresponding inserted parameters).Second, there's a new language fragment implementing a slight variation of standard lambda lifting, where we don't insert extra parameters for globally bound variables.
For example, previously
would get lambda lifted to something like
which is useful if you fully want to remove all closures, but redundant if you're fine with letting functions reference top-level values.