fix(go): return nil instead of panic when AST node has invalid position#197
Merged
wzekin merged 2 commits intoJun 1, 2026
Merged
Conversation
When parsing files with compilation errors, AST nodes can have End offset smaller than Pos offset, causing slice bounds out of range panic. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Duslia
approved these changes
Jun 1, 2026
wzekin
force-pushed
the
fix/recover-from-invalid-ast-position
branch
from
0bc6331 to
3668ead
Compare
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
wzekin
force-pushed
the
fix/recover-from-invalid-ast-position
branch
from
3668ead to
6df9391
Compare
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.
When parsing files with compilation errors, AST nodes can have End offset smaller than Pos offset, causing slice bounds out of range panic.
What type of PR is this?
Check the PR title.
(Optional) Translate the PR title into Chinese.
(Optional) More detailed description for this PR(en: English/zh: Chinese).
en:
zh(optional):
(Optional) Which issue(s) this PR fixes:
(optional) The PR that updates user documentation: