Good luck. In my experience C interop is one of Go's weakest points (and the main reason why I don't use it). Dragons lurk under the hood.
-
Doesn't mean it needs to be *easy* but it needs to be *possible* without using gross hacks that veer way off course from the expected usage.
For example, I usually do Python->C interop with Cython, and that works very well. Not everything is trivial but it's a *lot* nicer than Go.
-
-
I’ve worked with a lot of cross language/runtime bridges, but not with Cython. It sounds nice. Thanks for the heads up.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Well, Go has a fancier runtime than Python. That's the cost.
-
You can have a fancier runtime and still maintain flexibility. That argument is lazy.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.