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
It's not clear to me how slow CGo actually is for our usecase (and this whether #87 is actually justified). We can probably also tag all of our functions #cgo noescape and/or #cgo nocallback once we update to Go 1.24 (golang/go#56378).
The text was updated successfully, but these errors were encountered:
cyphar
changed the title
go bindings: benchmark CGo overhead and #cgo no escape/nocallback
go bindings: benchmark CGo overhead and #cgo noescape/nocallback
Oct 19, 2024
It's not clear to me how slow CGo actually is for our usecase (and this whether #87 is actually justified). We can probably also tag all of our functions
#cgo noescape
and/or#cgo nocallback
once we update to Go 1.24 (golang/go#56378).The text was updated successfully, but these errors were encountered: