How does this work? As far as I understand Go is moving to a copying collector, so any pointers passed to C may become wild pointers when garbage collection is performed.
On go-nuts, Go's developers have been warning that passing arrays to C by getting the address of the first element of the slice will be unsafe for this reason.
it's hard. mixing manual and automatic memory management is tricky.
I wonder, does this make stuff like this unsafe:
var thing C.thing; C.somefunc(&thing)
i.e. can stack address change now?
Create memory in Go-land
Use memory in C-land
Dispose of reference to memory in Go-land
To make things work, you have to allocate date used in C in C and pass Go variables only by value.