Ali Mohammad Pur

We could read it at runtime I guess, if we assume its location relative to the runtime dir.

Slowly moving, but I've got a partial implementation working in https://github.com/alimpfard/jakt/tree/sr. With the CTFE support present, it's relatively simple to do - just need some time to support enough to...

Some more relevant bits: - The current keypair gen algorithm is pretty much the fastest you can go without weird hacks - Almost all of the performance issues are currently...

Formatting trouble aside, LGTM.

Yeah the build instructions are most likely out-of-date. - clang 14: not sure about the stdc++ error, but clang-15 is the minimum requirement anyway. - g++: I think you're missing...

:thinking: why close the PR?

> WebAssembly.Memory.buffer must return the same ArrayBuffer every time and must grow in place as Wasm's memory buffer is expanded (required, as Ruffle keeps a cached reference to this ArrayBuffer...

Implemented that behaviour in #18079.

```js bulkMemory(), simd(), saturatedFloatToInt(), signExtensions(), referenceTypes(), ``` Of the listed extensions, the only currently unimplemented one in LibWasm is SIMD; - bulk memory was implemented in #17218 - non-trapping float-int...

:thinking: So either we make that function more complicated, or add a comptime way to invoke external commands and capture their outputs - I'm not a fan of either option...