Skip to content

Panic on poisoned parser mutexes in tree-sitter parsing#23

Merged
jssblck merged 1 commit into
mainfrom
jssblck/issue-13-parser-mutex-panic
May 28, 2026
Merged

Panic on poisoned parser mutexes in tree-sitter parsing#23
jssblck merged 1 commit into
mainfrom
jssblck/issue-13-parser-mutex-panic

Conversation

@jssblck
Copy link
Copy Markdown
Contributor

@jssblck jssblck commented May 28, 2026

Summary

  • Make tree-sitter parser lock failures explicit instead of silently turning poisoned mutexes into missing parses.
  • Keep syntax matching behavior honest: poisoned parser state now surfaces as a programmer error instead of returning None and hiding the failure.
  • Add a regression test that poisons a mutex and verifies the parser helper panics as intended.

Testing

  • cargo fmt --all --check
  • cargo test -p nudge
  • git diff --check

Resolves #13

Co-authored-by: Codex <noreply@openai.com>
@jssblck jssblck marked this pull request as ready for review May 28, 2026 23:24
@jssblck jssblck merged commit 21306d6 into main May 28, 2026
4 checks passed
@jssblck jssblck deleted the jssblck/issue-13-parser-mutex-panic branch May 28, 2026 23:24
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.

Parser mutex lock failures should panic, not silently fail

1 participant