This repository has been archived by the owner on Dec 1, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 110
Can companion declarations be avoided for private functions? #13
Comments
If you don't need them from Golang you should be able to leave them out. And maybe really make sure that they are private, or even inlined by the compiler. |
I marked functions Note that I applied my fix from #15 to fix the crash.
|
The ABI of go asm is different with C. I think the tool is missing concern this. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm trying to convert a big library which has many functions calling each other and just few of them are public. Nevertheless I have to write a lot of declarations in the companion file for all those private assembly functions, which is boring. Are they really needed for private functions?
The text was updated successfully, but these errors were encountered: