Andrew Hlynskyi

The problem with supporting predicates in the runtime library is that many predicates require access to a source test to make sub strings comparison while the query runtime just operates...

Just as an idea that came up to me. It would be possible to split the `tree-sitter.so` to a series of libraries: * `tree-sitter.so` - a pure algorithmic library without...

@mattmassicotte on a [previous](https://github.com/tree-sitter/tree-sitter/issues/2038#issuecomment-1386050341) message @maxbrunsfeld reasonably pointed that it's impossible to implement all currently supported predicates like `#match?` without integrating with some good regex library. In the C ecosystem...

@mattmassicotte I've got your point, I agree, it would be possible to support processing in the core library all _pure string_ predicates that actually don't contain any regex specifics in...

@stevenbarragan Thanks! That's one of the options I've discovered, but it requires some work for adaptation.

I also faced with this limitation when tried to implement a language grammar by following its specification but when I realized that for an editor it's better to have less...

> Currently, the languages write external scanners to support `seq` without `extras` in between. I wish we had a function like `immediate` to show this. The case with custom extras...

@ebkalderon I've updated most dependency crate versions to the latest to make that `tower-lsp` wouldn't be a blocker to use latest crate versions in the consumers' code but the `dashmap`...

[Confirmed](https://github.com/ghbrown/tree-sitter-chapel/tree/b85c0d92a010c839ced297982bcd839096a6ab48). It looks like a problem with parser termination on EOF: ```sh # ts g && ts p examples/declaration.chpl -d |& head -n300 ..... shift state:3 process version:0, version_count:1, state:3,...

Supertypes are seen in a `node-types.json` file, so it's possible to construct a reverse map for what types have super type predecessors. Also it possible to use a super types...