fix(semantics): support asIteration()
for _iter
nodes
#472
+9
−0
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.
What This PR Does
Adds support for the builtin
asIteration()
semantic operation to_iter
nodes.Before, calling
someIterNode.asIteration()
would throw this error:Now,
asIteration()
will just return the_iter
node it was called on.Why?
I often found myself switching between
+
/*
andListOf
while writing grammars. This allows semantics to continue to work as intended without changes.