Sqinn-Go VS ccgo

Note that Squinn is not "native go" or "go only", but the owner insists on misleading people:

https://github.com/cvilsmeier/sqinn-go/issues/8

If you want to avoid cgo, consider sqinn as well: benchmarks.

Of course, it may seem... odd to add a remote interface to an embedded database, but I think that it fits some niches well, especially when decoupling persistence and logic is needed, without renouncing to the expressivity of SQL. It was inspired by PostgREST, but it’s much more “low level” – and it should be even simpler to adapt to some cases. Also, it serves the same purpose of sqinn but with a more general interface.

Why don't you try a pure-Go implementation? Should have enough features implemented for basic use

https://github.com/cvilsmeier/sqinn-go

Is "ported" the right term here? It know the repo's README says "CGo-free port", but this is the C version of TCL transpiled from C to Go (see the ~13MB .go files per platform in the "lib" directory). Which is a very cool idea, and the author has done the same thing with SQLite, to avoid CGo (https://gitlab.com/cznic/sqlite).

Here's a link to his C to Go translator: https://gitlab.com/cznic/ccgo

Totally agreed: almost all users (me/GoAWK included) want performance and don't care nearly as much about simplicity under the hood. Simplicity of implementation is of value for educational purposes, but we could easily have a small, simple 3rd party package for that. Go's regexp package is kinda too complex for a simple educational demonstration and too simple to be fast. :-)

I actually tried BurntSushi's https://github.com/BurntSushi/rure-go (bindings to Rust's regex engine) with GoAWK and it made regex handling 4-5x as fast for many regexes, despite the CGo overhead. However, rure-go (and CGo in general) is a bit painful to build, so I'm not going to use that. Maybe I'll create a branch for speed freaks who want it.

I've also thought of using https://gitlab.com/cznic/ccgo to convert Mawk's fast regex engine to Go source and see how that performs. Maybe on the next rainy day...

FYI it uses facility to translate C to go (https://gitlab.com/cznic/ccgo), there is a similar project does the same thing (https://github.com/elliotchance/c2go).

It's not really pure go, it's transpiled using https://gitlab.com/cznic/ccgo

Just about all the code looks like this:

  // Call this routine to record the fact that an OOM (out-of-memory) error

It would be interesting to read a comparison against https://gitlab.com/cznic/ccgo