Skip to content

Fix for #513 - _ParseBinaryExpr builds a node whose range excludes it's children - #514

Open
Mark Beznos (vibbix) wants to merge 2 commits into
microsoft:mainfrom
vibbix:feature/fix-bad-range-for-calc
Open

Fix for #513 - _ParseBinaryExpr builds a node whose range excludes it's children#514
Mark Beznos (vibbix) wants to merge 2 commits into
microsoft:mainfrom
vibbix:feature/fix-bad-range-for-calc

Conversation

@vibbix

Copy link
Copy Markdown

This is the fix for #513 - "_ParseBinaryExpr builds a node whose range excludes it's children"

All that was needed was setting the node.offset back a bit. Added the test-suite from earlier, so it points correctly now.

@vibbix Mark Beznos (vibbix) changed the title fixed parser overshoot because the scan marker set's the current location, instead of the preparsed one Fix for #513 - _ParseBinaryExpr builds a node whose range excludes it's children Sep 4, 2026
@vibbix

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant