当C库使用不透明的结构指针时，如何解决cgo中“写屏障中的坏指针”的恐慌

I'm currently writing a Go wrapper around a C library. That C library uses opaque struct pointers to hide information across the interface. However, the underlying implementation stores size_t values in there. This leads to runtime errors in the resulting program. A minimum working example to reproduce the problem looks like this:I'm currently writing a Go wrapper around a C l