Seems like I'm back to obscurity.

:)

https://sqlite.org/vec1/doc/trunk/doc/vec1.md

Many of these flags are the equivalent of GODEBUG. GODEBUG does not have 1843 options, but do you know how many it has? Have you ever used GODEBUG? (I'm guessing no, hence, immaturity) And if not, do you think it should just be dropped because you never needed it?

Already using it for my SQLite driver, and already in use by some a few other projects: https://github.com/topics/wasm2go

evacchi does most of the maintaining these days, but I'll keep helping as best as I can.

Your harness looks interesting to replace wast2json with watgo in wasm2go. Though my current problem is that I should be using the JSON to decide which tests to run (manual process so far), and to generate the more complicated test files (e.g. the ones that link modules together).

Btw, if Eli reads this: thanks for the WAT samples, they were very helpful working on wasm2go!

That just means we need to structure cities differently.

I live in a 1 sq km neighbourhood (literally, 1 km square) that houses 10k people.

It has almost everything I could wish for at walkable distance, schools for all ages, parks, a gym, a pool, sports campgrounds, medics, pharmacies, stores, markets, etc.

What doesn't exist (e.g. a movie theater, a library) I can reach by public transit in half an hour. The city has 2M people, there's plenty of stuff to do.

I've lived here all my life, my kids go to school with the kids of my school mates. They walk to school from at least 10yo, they visit each other's houses. During school breaks and weekends, they play in the park with their school friends while their parents grab a beer in a nearby kiosk.

You can build communities like this within cities.

On Linux it's really as simple as installing QEMU binfmt and doing:

   GOARCH=s390x go test

Ideally, I'd like to be able to specify the stored type (or at least, side step numeric affinity), and give the type a name (for introspection, documentation).

Specifying that a column is a DATETIME, a JSON, or a DECIMAL is useful, IMO.

Alas, neither STRICT nor non-STRICT tables allow this.

That will not change, and I'm not sure how you expect that to work with zero human involvement.

https://research.swtch.com/bisect

TLDR: you can bisect on more than just "time".

The majority of the world thinks the Israeli/US-Iran war is illegal.

Iran hit an E-3's antenna in an airport in Riyadh with a precision strike. Was it not worth defending?

How many tankers inside the Gulf do they need to hit before the rest of the world decides it's a bad idea to send new tankers to the Gulf?

And if new tankers don't go into the Gulf, then it's simply not open for business. That's their leverage.

Particularly for my use case, Go cross compilation, QEMU and binfmt work really well together.

Still, for some things, it's nice to test on actual hardware.

Here's a workflow so you can see both approaches working: https://github.com/ncruces/wasm2go/blob/main/.github/workflo...