fix: parse tree-sitter sequence syntax as Seq instead of wildcard Tree
#277
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.
Summary
((a) (b))now parses asSeqnode instead of wildcardTreewith children((x))being interpreted as "any node containing x as child" instead of "sequence containing x"Why
Pattern
((expression_statement) @s)* @outerwas returning empty results because((x))was parsed as a wildcard node match + descend, rather than a single-item sequence. This broke tree-sitter compatibility for users migrating queries.