Oh yeah. I've been scarred by that from a past life. I feel your pain.
-
-
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 -
The requirements were defined and documented a few releases back. There's also a runtime check for the rules. No as bad anymore.
2 replies 0 retweets 0 likes -
Is there some kind of pinning mechanism for Go memory to avoid having to make copies?
1 reply 0 retweets 0 likes -
You can just share things directly, no copies required, in most cases. See https://golang.org/cmd/cgo/#hdr-Passing_pointers …
2 replies 0 retweets 0 likes -
I remember reading that at some point. It's still *very* restrictive. Works fine for flat buffers but data structures are hell.
2 replies 0 retweets 0 likes
E.g. the only way to follow those rules and use complex context-based callback APIs is to indirect through a map or similar.
-
-
I programmed things for the old QuickTime component manager — I can handle refcons and all those hoops just fine if I need it. :-)
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.