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
[UPDATE]
It turned out that we cannot simply export the func contains go interface. We have to cast this “back and forth", that is, implementing a corresponding C++ interface, then passing the implemented functions to Go, then using the passed functions to implement the native Go interface, and finally exporting Go APIs to C++ as a .h file. The details are in the associated branch.
[STALE]
As in #1, the plan is to exporting go APIs into shared libraries that can be called by c++. Since there are many APIs, I'm starting with init_login to verify if this way works, then apply to other APIs.
Currently the challenge is exporting interface type in Go, which is not explicitly documented in cgo.
Additional information
No response
The text was updated successfully, but these errors were encountered:
What would you like to share?
[UPDATE]
It turned out that we cannot simply export the func contains go interface. We have to cast this “back and forth", that is, implementing a corresponding C++ interface, then passing the implemented functions to Go, then using the passed functions to implement the native Go interface, and finally exporting Go APIs to C++ as a .h file. The details are in the associated branch.
[STALE]
As in #1, the plan is to exporting go APIs into shared libraries that can be called by c++. Since there are many APIs, I'm starting with init_login to verify if this way works, then apply to other APIs.
Currently the challenge is exporting
interface
type in Go, which is not explicitly documented in cgo.Additional information
No response
The text was updated successfully, but these errors were encountered: