Closes #23. Add support for operational assignments. #30
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.
The interpreter now nows how to visit
OpAssign
nodes, including the conditional assignment variants,||=
and&&=
. For normal cases, the node is simple rewritten fromtarget op= value
totarget = target op value
. For conditional assignments, the expansion is closest totarget op target = value
, but with some safeguarding to avoid raising errors whentarget
does not exist in the current scope (it will be initialized tonil
).This rewriting also works with Calls, where the assignments are rewritten to call the assignment variant of the method (i.e.,
#{method}=
) rather than performing aSimpleAssign
.See #23 for more details.