You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gopy currently (mostly) sends pointers to go values back and forth between cgo and go.
on the cpython side, such types are (usually) defined like so:
typedefvoid*cgo_type_pkg_MyType;
structcpy_type_pkg_MyType {
PyObject_HEADcgo_type_pkg_MyTypecgopy; /* pointer to pkg.MyType */
};
under the rules currently defined at golang/go#12416, this will no longer work as we store a pointer to go memory, possibly containing itself pointers to go memory.
so we'll probably have to bite the bullet and move to the (de)serialization protocol of golang.org/x/mobile/bind/seq.
The text was updated successfully, but these errors were encountered:
gopy
currently (mostly) sends pointers togo
values back and forth betweencgo
andgo
.on the
cpython
side, such types are (usually) defined like so:under the rules currently defined at golang/go#12416, this will no longer work as we store a pointer to
go
memory, possibly containing itself pointers togo
memory.so we'll probably have to bite the bullet and move to the (de)serialization protocol of
golang.org/x/mobile/bind/seq
.The text was updated successfully, but these errors were encountered: