Joel Dice

I agree that representing a `Row` as a WIT `resource` is the most natural option. Regarding `get`/`try_get` methods: since WIT does not support arbitrary generics, it may be necessary to...

@miketang84 You might find this interesting: https://github.com/theduke/wasi-sql/blob/main/schema/sql_v1_alpha1.wit

I would prioritize #643 first since that's likely to be a more stable platform for building a C++ SDK than the `wit-bindgen`-generated bindings.

@lann tells me he's working on a subset of this as part of a more general refactoring, FYI.

I think this could be a "good first issue" if we flesh it out a bit more, e.g. explaining where in the code to add context.

Honestly it's been a while since I did anything serious in either TS or JS, so my knowledge may be out-of-date. Last time I worked on a TS project, we...

Fair enough. The "Working with TypeScript-compatible transpilers" section of https://www.typescriptlang.org/download might be helpful. I don't have any experience with anything but `tsc`, unfortunately.

In case it's of interest, I've recently been experimenting with using TeaVM to build [Spin](https://github.com/fermyon/spin) apps: https://github.com/dicej/spin-http-java. Spin is based on [Wasmtime](https://github.com/bytecodealliance/wasmtime) rather than Wasmer, but model is generally the...

See https://github.com/konsoletyper/teavm/pull/610 for a patch which adds a `WASI` target, suitable for building modules which Wasmer, Wasmtime and other WASI-compatible runtimes can execute.

@konsoletyper First, thanks for all the work you've put into TeaVM. The WebAssembly support in particular is quite impressive and useful. I've looked at other similar projects, but TeaVM seems...