sabine

Thank you @wingo for linking how Schism implements its uniform value representation with the JavaScript GC in https://github.com/WebAssembly/gc/issues/53#issuecomment-545882853.

I had a look at the GC experiments in https://github.com/lars-t-hansen/moz-gc-experiments/blob/master/version2.md and the tests at https://hg.mozilla.org/mozilla-central/file/tip/js/src/jit-test/tests/wasm/gc/ which both look very interesting and promising. I could see us trying to directly compile...

Ah, I missed that `anyref`s from the reference types proposal can't be stored in the WASM linear memory directly (I don't know why I assumed that in the first place)....

I have an app where, in Elasticsearch, I have a mapping with nested documents. So, for some table `A` I have a mapping ``` { 'properties': { [..] 'B': {...

When you're writing a compiler, it could be convenient to use the browser to debug the generated code. Here, having the ability to see all the names that you deliberately...

Just two short points (overall, I'm happy with the Url API and routing facilities of Seed): 1. I would rename `UrlSearch` to `UrlQuery` because query is overall the more commonly-used...

> all functions that modifies the url directly in the browser window have prefix go (go_and_push, go_and_replace, go_back, etc.). They are basically slim wrappers for native History and Location api....

> You can also subscribe to subs::UrlRequested and interrupt it / modifies it / prevent UrlChanged firing. That way you can handle manually both programmatic redirects and link clicks. Btw,...

I see that WASM already has 64-bit integers, which suggests, that, eventually, WASM might be usable as a 64-bit compilation target. We are very interested in a spec that allows...

Ah, sorry about derailing. If all `(ref ...)` types must still be subtypes of `anyref`, then `(ref i63 ...)` is obviously not a reasonable thing to have.