Add exported map keys to local scope #377
Merged
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 fixes an inconsistency in behaviour between exporting values using assignment or maps.
This happens because map entries typically don't get added to the local scope. The runtime will look for a local value first, and then check the exports map if one isn't found. In this case, a local
y
is available, so the exported value isn't used. Exporting via a map is available for convenience and shouldn't have a difference in behaviour, so this PR ensures that map-export entries get assigned locally, updating existing variables if they exist.