Hector Martin

Be very careful with memory management. Last I used it, the requirements/guarantees wrt Go-owned memory were unclear/poorly documented.

The requirements were defined and documented a few releases back. There's also a runtime check for the rules. No as bad anymore.

Is there some kind of pinning mechanism for Go memory to avoid having to make copies?

You can just share things directly, no copies required, in most cases. See https://golang.org/cmd/cgo/#hdr-Passing_pointers …

I remember reading that at some point. It's still *very* restrictive. Works fine for flat buffers but data structures are hell.

I think that is an important point of any bridge between languages/runtimes: expect nothing but the simplest of data to work.

I respectfully disagree; I think well-designed FFIs should be able to accomodate almost every use case without ugly workarounds.

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.