Allow parse macro statement identifiers #17
Merged
Conversation
This file contains hidden or 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
jgonzac
requested review from
a team,
alvrogd and
igarcia0
and removed request for
a team
alvrogd
approved these changes
Oct 10, 2025
It's such a shame, but I think we can't do that here. We have no way to pass in the |
jgonzac
force-pushed
the
feature/AllowMacroExpressions
branch
from
1bd5b34 to
813d49d
Compare
Iñaki is right, we can't do it here. Although I added a test case in the other side checking the grammar tree output. |
igarcia0
approved these changes
Oct 13, 2025
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.
Allow parsing some basic macro statement identifiers