dcodeIO

Having a feeling that peak perf isn't the right motivation in context of this library. In practice it still emulates so fusing two ops seems neglectable?

As far as I know, and I know little, irregex, an implementation in Scheme, became the benchmark for browser RegExp with both Chrome and Firefox using it nowadays. Some random...

> So technically, we already have WebSockets in Node core, the question is, should we expand/improve this and **expose** this? A feeling tells me that node.js should have a `WebSocket`...

Btw, Tetris sound in the game type select menu (the one right after pressing start) is laggy here (FF and Chrome) 😢

Sadly it's the second, regardless of input 😢

Btw, the recommended portable way of writing this with AS is ```ts let positionIndexToAdd = i32(Channel3.waveTablePosition / 2); ``` which is a nop in WASM and a `|0` in JS....

Iirc the idea here is that `StaticArray#slice` returns an `Array` while `StaticArray.slice` works with `StaticArray`, like other instance/static methods, i.e. the static ones exist to provide what would otherwise be...

I guess the same would apply to other static methods as well then, and without inference of return types seems tricky. Hmm. Sure it wouldn't be better to defer until...

Is `cli/tsconfig.json` the right file for this change? A typical project would have an `assembly/tsconfig.json` extended from `assemblyscript/std/assembly.json` as per what `asinit` generates.

It could be that the correct file is the one `asinit` generates. Iirc, as soon as the earliest tsconfig has an `include` entry, it overrides what's in the extended base...