tree-sitter / tree-sitter/java-tree-sitter
Collect source bytes from ParseCallback
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 141
- Forks
- 34
- Avg merge
- 14d 2h
- Merged PRs (30d)
- 2
Description
We could instead remove this check and collect the bytes similar to https://github.com/tree-sitter/py-tree-sitter/pull/343 but I don't know how much of a performance impact this will have.
Originally posted by @ObserverOfTime in #105
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the ParseCallback implementation in the Java bindings and review the linked py-tree-sitter pull request for the comparable byte-collection approach. Assess the performance impact and identify the behavior and tests that would demonstrate source bytes are collected correctly; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100