libc VS sqinn

I don't think I understand what the argument for that is, because I've only ever heard it articulated as "cgo isn't go" which doesn't really convey much information.

Is this go? https://gitlab.com/cznic/libc/-/blob/master/libc_openbsd.go?...

I mean technically I suppose it is code that conforms to the go language grammar, but I'm not sure why a language purist would accept this.

Maybe you can contribute a fix? The related discussion is here: https://gitlab.com/cznic/libc/-/issues/20

First part of the README that hasn't changed in 2 months:

> Sqinn-Go is a Go (Golang) library for accessing SQLite databases without cgo. It uses Sqinn https://github.com/cvilsmeier/sqinn under the hood. It starts Sqinn as a child process (os/exec) and communicates with Sqinn over stdin/stdout/stderr. The Sqinn child process then does the SQLite work.

> If you want SQLite but do not want cgo, Sqinn-Go can be a solution.

This seems pretty clear to me about what's happening. It makes an OS call to a third-party executable (sqinn), pipes the result from stdout back into the Go code. The advantage is you don't have to compile the C code alongside your Go code.

Honestly, I don't really know how much more clear the author could be. I guess if you don't know what stdin, stdout, and stderr are it might be confusing? It's hard to imagine that a programmer who is interested in this library isn't familiar with those concepts though.

I've not used it, but sqinn is one sqlite server meant specifically to be used by languages without c calling conventions:

https://github.com/cvilsmeier/sqinn

The latest supported version is 3.38.3: https://github.com/cvilsmeier/sqinn/releases/tag/v1.1.15