Catherine
Catherine
Do not expect me to fix this.
That's a [documented incompatibility](https://github.com/whitequark/parser#u-escape-in-18-mode). I've looked at it and deemed it unworthy of fixing because of miniscule impact and severe changes required to lexer.
FWIW I think this should be added to README and then closed, too.
Huh? When did that happen?
@guybedford So while working on this I bumped into a question, namely, why do we have separate `getCoreModule` and `instantiateCore = `? This seems to serve no purpose and creates...
Oh. That's of course not possible because later modules can depend on earlier ones.
OK so this actually looks to be quite challenging with JCO's architecture. To recap, right now the generated code for `--instantiate async` looks like this: ```js export async function instantiateAsync(getCoreModule,...
You might ask, "why not simply extract the `Module` from a fulfilled `Promise` when `getCoreModule` returns one? I thought I'd do that at first, but it seems that there is...
> unless we entirely emit two instantiation wrappers - `instantiateAsync` and `instantiateSync` where you select which one to use at the top-level for a runtime decision. This would be by...
> Surely not more than a few hundred lines of JS? I was thinking of that yeah. I suppose that compared to the megabyte-sized wasm blobs that I ship it's...