Zig 0.15.1 "Writergate" support

[mfeineis]

Hello there, I've been upgrading one of my own projects to Zig 0.15.1 and my most important dependency is zig-tree-sitter right now. I've got a local fork I'm working on, nothing major done yet just a dependency upgrade.

Would there be interest in getting those changes back into upstream, once they're ready? If you already have something brewing yourself feel free to close this issue otherwise I'd be happy to contribute.

I see the following things that need to be done/decided:

• 1. Managed Zig containers have been deprecated so my plan would be to change the zig-tree-sitter APIs that use managed containers to use unmanaged variants instead, this'd be a breaking change as the user needs to supply their own std.mem.Allocator to every one of those calls. Another possibility would be to just use the renamed variants that are still in 0.15.1 but then another pass to remove the deprecated API usage - including another breaking change - would be necessary in the near future, likely in the October-end of the year time frame.
• 2. The "writergate" changes in std.io mainly seem to impact the formatting functionality of the various structs since the signature of the format function has been changed
• 3. Probably more I've not stumbled across yet :-)

Cheers!

[McSinyx]

Uses of ArrayList are actually broken and the API would be more idiomatic to return slices instead, like in GH-24.

[mfeineis]

Uses of ArrayList are actually broken and the API would be more idiomatic to return slices instead, like in GH-27.

Very nice, thanks for sharing your upgrades. I've been thinking about more intrusive updates too but I didn't want to overhaul the whole thing because I basically only use a fraction of the API provided. Maybe I should just bite the bullet and write my own wrapper around tree-sitter but I'm worried that I won't be able to keep up with the changes. tree-sitter is my main dependency and it's always a hassle to upgrade it but it's also very, very useful.

Just FYI: the Github issue link just points back to this issue, thanks again!

[amaanq]

Should be fixed in #30