Andrew Hlynskyi

Hmm, your example doesn't reproducible for me: 

Also hit to this issue: https://github.com/tree-sitter/tree-sitter/actions/runs/4624890814/jobs/8180161810#step:5:67 It would be better to give cache key construction to outer scope. @mymindstorm please don't do this: https://github.com/mymindstorm/setup-emsdk/blob/ab889da2abbcbb280f91ec4c215d3bb4f3a8f775/src/main.ts#L31 A code like the next is...

@ahelwer Thank you for the awesome documentation improvements! Merged.

@mattmassicotte Thanks, I marked this PR to don't forget and will review it soon.

> Yeah, it’s a bug that the field shows up at all in that case. The node is hidden, and doesn’t contain any visible nodes, so the field should do...

Now it's possible with `tree-sitter generate -b --libdir .` and you'll find the builded `*.so` file in your current directory.

This will be resolved with #1262

Similar to: #235

@Aerijo As a workaroud for now, you can set some environment variables in your parser calling code and read that env variables only once on an external scanner initialization phase.

I'm not sure that it may be _Sync_ and _Send_. If to look to the `TSNode` struct and its constructor function: https://github.com/tree-sitter/tree-sitter/blob/c7998d93d0d180e0c11924e3f1543e1b0e4487be/lib/include/tree_sitter/api.h#L92-L96 https://github.com/tree-sitter/tree-sitter/blob/c7998d93d0d180e0c11924e3f1543e1b0e4487be/lib/src/node.c#L17-L28 And their counterparts in the Rust binding:...