I was the person who came in with the issue. My initial request was actually documentation since I found the docs that said I should be running the C.free() myself anytime a C.CString() is allocated. The confusion came when I expected the GC to free that on it's own since I was running it in a similar fashion to an inline cast (term used loosely here). So a note in the docs would be incredibly helpful. Additionally, the docs would also be more helpful if they explain that C.free() doesn't just show up when one does an import "C" and that they will likely need to include <stdlib.h> inside the comment section with compilation arguments. Both of those things would have been incredible time savers.

Let's start with documentation and move to vet if someone can show this meets the frequency bar.

This looks fixed. In golang.org/cmd/cgo I see:

// Go string to C string
// The C string is allocated in the C heap using malloc.
// It is the caller's responsibility to arrange for it to be
// freed, such as by calling C.free (be sure to include stdlib.h
// if C.free is needed).
func C.CString(string) *C.char

So both the fact that the caller must free and the note about stdlib.h are already there.

Closing.