Fix not operator parsing bug#75
Merged
martin-henz merged 2 commits intosource-academy:mainfrom Feb 9, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 fixes #74. The bug occurs as the parser assumes
previousTokenwill not be undefined, but it can be if the token is the first in the program. We can also consider enablingnoUncheckedIndexedAccessintsconfig.jsonto fix similar issues in the future, but it would require quite a bit of effort in fixing compile errors in our codebase at the moment.The change from switch-case to if-else is not necessary and is merely a style change; the effective change is changing
previousToken.typetopreviousToken?.type.