Thanks very much for your replies. I guess the killer argument is that
finalizers are not guaranteed to run! I didnt know that. Just to be clear,
Im not intending exposing WrappedString to my clients only standard go
strings, everything *should* be freed up when my outer wrapper function
exits
> On Oct 17, 2016, at 5:03 PM, andrew.sm...@miracl.com wrote:
>
> Hi,
>
> When using cgo its my understanding that strings created with C.CString must
> be freed with C.free, but yet numeric types do not need to be explicitly
> freed.
Yes. This is because strings in C are not first class obje
