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
Refactored
if-end
jump logic forif-condition
state. Related to issue #9.If-body
block stateFor the
if-body
block state, when calledreturn
anyway after this theJumpTo if-end
instruction is called. It's redundant, refactored, and added an additional checks for label instructionJumpTo
ismanual-return
for the current block state. Ifmanual-return
is setJumpTo
context instruction is removed.function-body
block stateFor the
function-body
block state should be added an additional check formanual-return
. If it is set totrue
add the labelreturn
before thereturn
instruction and also add thereturn
instruction itself.Other cases
if-else
statement and refactored.if-else-if
statement - doesn't exist.loop
statement, as a conclusion: it's the only case for theif-condition
statement.