You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main difference I'm seeing is the use of cgocallback within the cgo calls. Is this c calling back into golang? Is that necessary?
In this scenario the performance was ~40-50% slower then smacker. Note the 3 main blocks shown are the Tree.Close(), QueryMatch.Next() and ParseWithOptions() calls:
smacker (21s total):
tree-sitter (29s total):
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
I'm looking to switch from https://github.com/smacker/go-tree-sitter but I'm finding the performance of https://github.com/tree-sitter/go-tree-sitter to be noticeable slower.
The main difference I'm seeing is the use of
cgocallback
within the cgo calls. Is this c calling back into golang? Is that necessary?In this scenario the performance was ~40-50% slower then smacker. Note the 3 main blocks shown are the
Tree.Close()
,QueryMatch.Next()
andParseWithOptions()
calls:smacker (21s total):

tree-sitter (29s total):

The text was updated successfully, but these errors were encountered: