nvim-treesitter / nvim-treesitter/nvim-treesitter-textobjects
Performance
Open
Nobody has claimed this yet.
bug
- Dominant language
- Tree-sitter Query
- Stars
- 2.8k
- Forks
- 271
- Avg merge
- 8d 8h
- Merged PRs (30d)
- 1
Description
Describe the bug
Current search for textobjects is too slow and could be more flexible (counts, textobjects in same line).
Solution
Avoid iter_prepared_matches in find_best_match. Use find_best_matches to allow the use of v:count
Contributor guide
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
Locate find_best_match and compare its use of iter_prepared_matches with find_best_matches; start by reading how textobject searches and v:count are handled. Done means the search is faster and supports counts and multiple textobjects on the same line without using iter_prepared_matches in find_best_match.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100