Properly raise SyntaxError for various mis-nested If/Elif/Else statements #610
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.
This patch generalizes the fixes to #500 to correctly raise
SyntaxError
instead of silently doing the wrong thing for the statementsElif
insideIf
,Else
insideIf
,Elif
insideElif
, andElse
insideElse
.There are also new tests for these cases. Additionally there are new tests to verify the correct SyntaxError for
Case
insideCase
,State
outside ofFSM
, andState
insideState
(though their behavior was already correct and was not changed).