-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Index assignment gotchas #315
Comments
odino
added a commit
that referenced
this issue
Feb 11, 2020
They were not properly handling the case where the final character is a `;`, when they should "consume" it and move forward. Instead, the parser would parse the assignment and move onto the next block, which was a single `;`, causing it to fail. A better fix for this could be allowing `;` as valid blocks that are simply ignore, which would also solve expressions such as `x = 1;;;`, which are now erroring out.
odino
added a commit
that referenced
this issue
Feb 11, 2020
They were not properly handling the case where the final character is a `;`, when they should "consume" it and move forward. Instead, the parser would parse the assignment and move onto the next block, which was a single `;`, causing it to fail. A better fix for this could be allowing `;` as valid blocks that are simply ignore, which would also solve expressions such as `x = 1;;;`, which are now erroring out.
odino
added a commit
that referenced
this issue
Feb 11, 2020
They were not properly handling the case where the final character is a `;`, when they should "consume" it and move forward. Instead, the parser would parse the assignment and move onto the next block, which was a single `;`, causing it to fail. A better fix for this could be allowing `;` as valid blocks that are simply ignore, which would also solve expressions such as `x = 1;;;`, which are now erroring out.
Fixed in |
odino
added a commit
that referenced
this issue
Feb 11, 2020
They were not properly handling the case where the final character is a `;`, when they should "consume" it and move forward. Instead, the parser would parse the assignment and move onto the next block, which was a single `;`, causing it to fail. A better fix for this could be allowing `;` as valid blocks that are simply ignore, which would also solve expressions such as `x = 1;;;`, which are now erroring out.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: