Comment 2 for bug 1535157

I can't claim to know how to fix this properly. Maybe ask on golang-nuts?

On 19 January 2016 at 07:02, James Henstridge
<email address hidden> wrote:
> What we want to do is pass a string down to the C/C++ wrapper without
> copying the data: the APIs don't take C strings, so we'd need to make
> yet another copy if using C.CString(), and would also need to deal with
> memory management of that copy.
>
> The function doesn't hold a reference to the memory past when it
> returns.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1535157
>
> Title:
> breaks go 1.6 cgo pointer rules
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/go-unityscopes/+bug/1535157/+subscriptions