Dan Kortschak

@ianlancetaylor, to follow this up, I'd like to clarify the position on having a C pointer, backed by an allocation be `C.malloc`, which is populated with a shallow copy of...

Thanks. I figured that, but wanted to check. I guess that leaves us with the task of writing a generic deep copy function from Go to C memory. I have...

@sbinet @TacoVox While I was looking at the finalizer problem I was also consider what we will do here. We need a deep copy routine for moving GoC, but we...

Can you provide background please. I had not heard anything about this.

Wow! That's not good.

https://github.com/rakyll/statik?

It looks like the inc between elements is wrong for integers.. Notice that in all cases we see the Go data [a, b, c] end up being written out as...

C `int` is almost always 32 bits on machines with 32 and 64 bit architectures (certainly for all the architectures that gc targets). Go `int` is 32 bits wide for...

This needs to be reviewed. I don't have time to do that right now, but other people may be able to.

It would need to be merged first, and then it will be included in the next minor release. In order to be merged it needs to pass review, which will...