Would love to hear more. I'm surprised both at C++ embedding Go (works, but rarely used) and also that curl gave you any problems. /@bagder
-
-
yes, I'm also very interested in as many and deep details as possible!
1 reply 0 retweets 2 likes -
Blog post or mail a mailing list and link thread here?
1 reply 0 retweets 0 likes -
Sounds like a good idea. tl;dr: libcurl is great, but OpenSSL threading sucks.
1 reply 0 retweets 3 likes -
Oh yeah. I've been scarred by that from a past life. I feel your pain.
1 reply 0 retweets 1 like -
Can you do this with zero copy?
2 replies 0 retweets 0 likes -
Haven’t gotten that far yet on performance tuning. Just some basic stuff, getting it working. It’s my first mix of C & Go.
1 reply 0 retweets 0 likes -
Replying to @willie @jimmyzelinskie and
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.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @jimmyzelinskie and
Anything in particular I need to be aware of? My tests have been intentionally simple so far.
1 reply 0 retweets 0 likes -
Replying to @willie @jimmyzelinskie and
Be very careful with memory management. Last I used it, the requirements/guarantees wrt Go-owned memory were unclear/poorly documented.
2 replies 0 retweets 1 like
My first Go app ended up with a Go->C->Go call chain and I hit a bug in the runtime (that had been reported and unfixed for a year or so)
-
-
I ended up debugging and fixing it, but what I saw about the innards scared me off of using Go more, especially mixing with C. :(
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.