Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

go bindings: should we try to use rustgo (no cgo)? #87

Open
cyphar opened this issue Oct 10, 2024 · 0 comments
Open

go bindings: should we try to use rustgo (no cgo)? #87

cyphar opened this issue Oct 10, 2024 · 0 comments
Labels
ideas welcome An open problem which doesn't have a clear resolution.

Comments

@cyphar
Copy link
Member

cyphar commented Oct 10, 2024

cgo function calls are quite expensive (~20x) and so there might be an argument that we should try to do some Go assembly hacks to try to avoid using cgo. On the other hand, there are obvious maintenance issues with magic assembly code, and it's not clear that the (real) overhead of cgo is a practical issue.

Food for thought...

Some links:

@cyphar cyphar added the ideas welcome An open problem which doesn't have a clear resolution. label Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ideas welcome An open problem which doesn't have a clear resolution.
Projects
None yet
Development

No branches or pull requests

1 participant