"When we've initially started [..], dominant was Go 1.3, which had mechanisms to detect memory blocks allocated inside used libraries and all such blocks were to be freed by GC. Go 1.6 significantly improved its memory management, however as part of those improvements memory allocated by external libraries was no longer garbage collected by the runtime."<p>This looks like a serious API break.<p>To be fair, the whole idea of the runtime automagically managing external memory gives me shivers, and this looks like moving in the right direction - I just think it was not very wise to go with that initial decision in the first place.
"var output = (*byte)(unsafe.Pointer(m))" This will give you the pointer to the byte slice object which may have its own structure which is opaque to you and this is not same as "getting the pointer to C byte array". It is weird that it was producing correct results at all :)
This remember me one of the Go Proverbs, Cgo is not Go <a href="https://www.youtube.com/watch?v=PAAkCSZUG1c&t=12m37s" rel="nofollow">https://www.youtube.com/watch?v=PAAkCSZUG1c&t=12m37s</a>