Added support for shadowing variables #411
Merged
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
djc
reviewed
Dec 25, 2020
|
Looks good, just a minor question! |
djc
approved these changes
Dec 25, 2020
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.
Fixes #329
Considering that it wasn't previously possible to shadow variables. Then this qualifies as a non-breaking change, as it only extends new functionality.
initializedtoLocalMetaIn short, if a
LocalMetaisinitializedthen any subsequent{% let ... %}shadows and generates a new variable. The variable is literally redefined byinserting a new one. Thereby making it possible to e.g. initialize and shadow in multiple nested branches.To be consistent with Rust,
{% let (a, b) = ... %}always shadows, and can't be used to assign (which it couldn't before either.)