W@ng
W@ng
Hi @ivar-rummelhoff Thanks for reporting. I'll fix this in the next release.
fixed in `v0.22.6a` .
Hi @hollowdjj There are no Python equivalents for now. The best solution i can think of is ```java byte[] bytes = src.getBytes(StandardCharsets.UTF_8); int startByte = node.getStartByte(); int endByte = node.getEndByte();...
A memory leak occurs during use, and the memory occupied by TsTreeNode cannot be automatically used.
Hi, `ts_tree_delete` will be called when TSTree object is garbage collected by JVM. In my opinion, it is a more natural way to do this in a garbage-collected language.
A memory leak occurs during use, and the memory occupied by TsTreeNode cannot be automatically used.
Hi, could you paste a test case here? That will be helpful.
A memory leak occurs during use, and the memory occupied by TsTreeNode cannot be automatically used.
Hi, @msb8080 Thanks for reporting. The issue was fixed in 0.22.5a. About the bytes length difference, Java use utf16 by default, tree-sitter use utf8 internal, this may cause the problem.
A memory leak occurs during use, and the memory occupied by TsTreeNode cannot be automatically used.
@msb8080 yes
A memory leak occurs during use, and the memory occupied by TsTreeNode cannot be automatically used.
@chenzhf2019 This issue is caused by how java dealing with UTF-8 strings. Java uses [Modified UTF-8](https://en.wikipedia.org/wiki/UTF-8#Modified_UTF-8) strings instead of normal UTF-8 strings. Planned to fix this in the next release.
A memory leak occurs during use, and the memory occupied by TsTreeNode cannot be automatically used.
> > Hi, > > `ts_tree_delete` will be called when TSTree object is garbage collected by JVM. > > In my opinion, it is a more natural way to do...
Hi, thanks for your contribution, but I prefer to keep the build script simple for now.