fix: handle unexpected tokens when parsing stabs #76
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.
Fix #75
The issue was that
stab_statewas leaking into inner stabs, corrupting the parser state and causing the wrong tokens to be handed toparse_stab_expression. Resetting the state seems to fix this. The other solution I found was to add a fallback clause toparse_stab_expressionbut that felt too hacky because we were still dealing with corrupt parser state.Also adds a bunch of tests for stabs to make sure the
stab_statelogic is not breaking anything else