Fix else if parsing problem #833
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.
Description
This PR fixes a problem related to parsing nested if/else in Colang 2. The problem is that whenever there is an
ifinside anelse, the parser considers that as anelifnode. However, this could be problematic, as theifmight not meant to be anelifto the outerif. Consider the following examples:This example results in parsing error. This is because the
elsestatement of the outerif, is combined with theifafter that and is considered aselif. Therefore, the lastelsestatement is not parseable, because there is noifrelated to that anymore! If you add anything betweenelseand theif, even an optional:or a comment, it will fix the parsing issue.In this PR, I changed the
_ELSE_IF.1definition, so it will capture any whitespace, except newline, between anelseandif.I have also attached the parsed tree, corresponding to the following code (removing the very last
elsefrom the above, so that it could be parsed).As you can see in the tree, the inner

ifis parsed aselif, not a nestedif.The correct form, which is the result of this PR, is this:

Checklist
@Pouyanpi @drazvan @schuellc-nvidia