Ryan Hileman

Probably. I think I mentioned in the Haskell thread, tree sitter probably needs a better standardized approach to building C++ parsers.

ah perfect. let me get the test-haskell branch up to date with that then close this PR, this issue is where I got stuck previously

Haskell looks to be failing on Windows Python 3.5 runner even with the new C parser: https://github.com/tree-sitter/py-tree-sitter/runs/5104795690?check_suite_focus=true

Note there's another type stub I linked in this issue: https://github.com/tree-sitter/py-tree-sitter/issues/58

@DorianCzichotzki were these manually written? I believe you don't need the `...` if you also have a docstring.

I just need to find some time to merge the two approaches and update the stubs.

@maxbrunsfeld thoughts?

serialize how, exactly?

There are two major problems I see here: The tree sitter C api uses opaque structs, such as [TSTree](https://github.com/tree-sitter/tree-sitter/blob/master/lib/include/tree_sitter/api.h#L40), which there's no way for the Python bindings to serialize (the...

I will likely get around to an official compiled package with languages embedded but I don't see an issue with posting an alternative on pypi in the interim. To reduce...